"TW" == Thomas Wouters <thomas@xs4all.net> writes:
>> I followed the instructions[1] on SourceForge to get mail sent
>> to my development list about CVS commits. Someone requested
>> unified diffs instead of context diffs, and I agreed, so I made
>> the following patch to syncmail, which passes the "-u" and
>> "--minimal" flags to CVS diff, and which strips out unnecessary
>> (to me) header lines from the cvs diff output.Fred was just musing that the syncmail script, is both a historical misnomer, and seems to be used in a lot of projects now. He wondered whether we should rename it and make it more available to the SourceForge community at large. I'd be all for that, and am willing to add it as a Python snippet on SF.
TW> Uhm, I'm right in assuming this changes it for *all* checkin
TW> messages, and not based on who gets the message, right ?Can't do that, unless you have two recipient lists. I never thought the diff style was worth going to all that extra trouble.
TW> I hope Barry doesn't apply it then ;) I used to prefer unified
TW> over context, but the python-checkins list has made me seen
TW> the light. Context diffs make it much easier to see both the
TW> old and the new code. This is highly personal, of course ;PThomas will laugh at me now, but I've been trying to teach/force myself to use unified diffs in my private environment. I think I'm getting the hang of them, but I /still/ find context diffs easier to read.
TW> Isn't there a tool that translates context diffs to unified
TW> diffs and vice-versa (if Barry does apply this patch, I will
TW> need it myself ;)Never heard of one. I think context diffs still make the most sense for syncmail.
-Barry