I have noticed that the whitespace in the source code is made up of a messy mixture of spaces and tabs. This may not seem important (because it isn't) but it does make looking at diffs a little confusing.
It is easy and safe to convert the whitespace at the start of each line to use tabs where possible: the command unexpand(1) does the trick. It is more dangerous to convert whitespace in the middle of a line because it might be inside a string constant -- I don't recommend this. The one trouble is that diffs of files from before the canonicalization and after are full of unimportant changes. diff's -b flag can fix that, but it is annoying. This makes it awkward if there are outstanding patches. I recommend doing all whitespace canonicalization. I recommend doing all source files at once, as a single change (not mixed with other ones). I recommend that it be done when there are few outstanding patches. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
