Gnus development mailing list
 help / color / mirror / Atom feed
From: Romain Francoise <romain@orebokech.com>
Subject: Re: Changes committed gnus/lisp (ChangeLog gnus-art.el)
Date: Thu, 30 Jun 2005 07:37:06 +0200	[thread overview]
Message-ID: <87ll4stngd.fsf@orebokech.com> (raw)
In-Reply-To: <muxbr5oeoee.fsf@uzeb.lrde.epita.fr> (Didier Verna's message of "Thu, 30 Jun 2005 01:25:45 +0200")

Didier Verna <didier@xemacs.org> writes:

> Look. There should *never* be any trailing whitespace in source
> files. If there are some, then the concerned committers are wrong. Not
> me.

I couldn't agree more, but you're missing the point.

> Personally, I never see any whitespace difference in diff's. Not even
> in cvs diff's (that explains why I did not understand your complain
> about the typo on top of the message).

Whether or not you choose to see it, deleting it does change the file
and makes it harder to track changes, creates unnecessary conflicts when
branching, etc.

-- 
Romain Francoise <romain@orebokech.com> | Sometimes I don't know where
it's a miracle -- http://orebokech.com/ | this dirty road is taking me,
                                        | sometimes I can't even see
                                        | the reason why.



  reply	other threads:[~2005-06-30  5:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1DneB5-0007RY-00@quimby.gnus.org>
2005-06-29 17:37 ` Romain Francoise
2005-06-29 23:25   ` Didier Verna
2005-06-30  5:37     ` Romain Francoise [this message]
2005-06-29 23:17 ` Faces of the wrong order (was Re: Changes committed gnus/lisp (ChangeLog gnus-art.el)) Katsumi Yamaoka
2005-06-29 23:40   ` Faces of the wrong order Didier Verna
2005-06-29 23:59     ` Katsumi Yamaoka
2005-06-30  3:18       ` Katsumi Yamaoka
2005-06-30 14:15         ` Adam Sjøgren
2005-07-01 14:34   ` Didier Verna
2005-07-01 16:05     ` Katsumi Yamaoka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ll4stngd.fsf@orebokech.com \
    --to=romain@orebokech.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).