|
From: Nick T. <nic...@ag...> - 2005-07-11 11:52:34
|
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... -- > Nick Thompson > Agere Systems Ltd |