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

Romain Francoise <romain@orebokech.com> wrote:

> "Didier Verna" <didier@lrde.epita.fr> writes:
>
>> -	because I just could't understand how to quote the list properly. 
>> +	because I just could't understand how to quote the list properly.

> please also fix this kind of thing. 

        ??? I don't know where you got that from. I did not write this, so I
don't see how I could fix it. Besides, I can't find a trace of the message
you're replying to on ding@.


> If you're removing whitespace (which you probably shouldn't without
> prior coordination),

        ??? ??? It's been *years* that whitespace auto-removing is the way to
go. Admitedly, it's been a while since my last commit to gnus, but this has
never been a problem before and I don't see why it should be one now. Or
things got really *that* bad since I took some distance from the project ?


> And at the very least, use separate commits for code and whitespace,
> otherwise tracking changes becomes a real nightmare.

        You have got to be kidding me right ??

Hmmm, ok. I see where the original message comes from. It's on gnus.commits. 
So maybe I should subscribe to this. Look. There should *never* be any
trailing whitespace in source files. If there are some, then the concerned
committers are wrong. Not me. 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). So maybe you
should just learn how to use -t -b -B -w.

BTW, the messages on gnus.commits should also avoid displaying whitespace
differences. And something else: please don't mail me directly when also
posting to ding@. I'm on it. This would not happen if the commit messages did
not appear as being sent by me (because I did *not* send it) but by the cvs
daemon. And what's more using the wrong address[1] (@lrde.epita.fr) because my
patch originates from @xemacs.org.

Geeze, some things *are* broken :-(



Footnotes: 
[1]  I don't know where the cvs daemon got that address from. The ssh key
maybe ?

-- 
Didier Verna, didier@lrde.epita.fr, http://www.lrde.epita.fr/~didier

EPITA / LRDE, 14-16 rue Voltaire   Tel.+33 (1) 44 08 01 85
94276 Le Kremlin-Bicêtre, France   Fax.+33 (1) 53 14 59 22   didier@xemacs.org



  reply	other threads:[~2005-06-29 23:25 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 [this message]
2005-06-30  5:37     ` Romain Francoise
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=muxbr5oeoee.fsf@uzeb.lrde.epita.fr \
    --to=didier@xemacs.org \
    /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).