|
From: Joachim E. <joa...@gm...> - 2005-07-13 21:16:08
|
Am Montag, 11. Juli 2005 13:52 schrieb Nick Thompson: > Hi, > > In some situations, it is required to follow up a merge with other actions. > File check-in or bug report updating for example. In these situations, it > would be useful to know what files were merged. Of course it might well be > possible to scan the before and after dir trees to find changed files, but > this might a long job in a big tree. > > So, my suggestion: Add an option to kdiff3 to request a merge report to be > generated on exit (stdout or file). This could list files actually merged > (saved), files that differed but were not merged and maybe some other > statistics. The output should be formated with an eye to it being > automatically post-processed. > > What do you think? > > Thanks for reading... Yes, I agree about that this would often be very useful. It's on my todo list, but currently development is slowed down somewhat. Nevertheless thanks for writing, Joachim |