Hans Meine wrote: > Hi, > > I hope I am not committing a sin by manually posting to -cvslog; this will > really only concern the core developers I guess:
Just use the devel list, I guess that is easier and cvslog always sets reply-to to the devel list anyway. > I am using some emacs code that makes sure that there is no trailing > whitespace in my source code; occasionally this will remove trailing > whitespace existing in SVN Can you give me that snippet? I once had a hook that stripped whitespaces on every safe which was a bad idea when editing signature files. :) I would like to have it only active for Python mode. > so my commits would be slightly bloated. In the end, the goal of > this tool is of course the opposite: if everyone used it, there > would not be such no-op changes. I also prefer no whitespaces. Before checking in I try to remember to call delete-trailing-whitespace. > When posting patches for review, I am using the following alias in order to > make the .diffs as readable as possible: > alias svndiff='svn diff --diff-cmd `which diff` -x -ubd' > > Now my question is: Should I take extra case not to commit such changes? > An example would be the attached tiny .diff, half of which is a no-op change > (removing a tab at EOL). I would prefer to have all trailing whitespaces removed anyway. What do other people think? Dischi -- There are 2 major products that came out of Berkeley: UNIX and LSD. We don't believe this to be a coincidence. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
