(As a side note: I've been a committer in a couple of Open Source projects for the past 10 years. I have noticed a funny thing about the first commits - they almost inevitably go wrong. You either commit some scratch files, or break the whitespace, or commit to a wrong branch, or accidentally delete the whole package... you know, this sort of things. It just occured to me it would be worthwhile to remind you about this well-established principle, just in case... ;-) )
I did notice that at least one of your patches used carriage returns instead of newlines. The Nutch code uses newlines as its end-of-line convention. There are a few 'fixcrlf' calls in build.xml to repair this for generated sources and documentation. Perhaps we should have one in another task (compile? test? a new task?) that normalizes ends of lines for edited code prior to checkin. What do you think?
Java doesn't care about the end of line convention, and most editors can handle both equally well, but CVS diffs seem to get confused when someone changes only a few lines but also changes the end-of-line convention on the entire file. Even 'cvs diff -w' doesn't really help. So, unless someone has a good workaround for this, I think it is best to keep the repository newline-based.
Doug
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Nutch-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nutch-developers
