If I recall, when I originally setup the git-trac server, I included a hook that would reject/warn any introduction of new trailing whitespace. I believe this was a compromise made after a long discussion at a Sage days -- there were a lot of concerns at the time about the effort required to rebase mercurial patches with conflicts arising from a whitespace patchbomb. I also believe that we included in the documentation and server side hook a suggestion to use the trailing whitespace stripping commit hook (and there was a sage-dev command that would automatically do that, although sage-dev has now been removed in favor of vanilla git or Volker's git trac).
On Tue, Feb 20, 2018 at 12:47 PM, Jeroen Demeyer <j.deme...@ugent.be> wrote: > Interesting fact: the number of lines with trailing whitespace is > generally *increasing* with every Sage release. So it seems to me that the > biggest problem (if you find whitespace a problem) is preventing new > whitespace. > > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. > -- Andrew -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
