From: Didier Verna <didier@xemacs.org>
To: ding@gnus.org
Subject: Re: Mixing whitespace and topical changes
Date: Thu, 19 Apr 2007 09:17:17 +0200 [thread overview]
Message-ID: <mux8xco7s02.fsf@uzeb.lrde.epita.fr> (raw)
In-Reply-To: <v93b2xbdxi.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed\, 18 Apr 2007 22\:55\:21 +0200")
Reiner Steib <reinersteib+gmane@imap.cc> wrote:
>> Now, this part really upsets me :-( [...]. Gnus is an
>> independant project,
>
> If Gnus wasn't a part of Emacs, we would not have to require a
> copyright assignment for non-trivial contributions (you also signed
> it, so you should be aware of it).
Of course. Although I can't remember exactly whether I signed
for a GNU software, or for GNU Emacs specifically. But in any case, you
can't deny that Gnus a somewhat "special" part of GNU Emacs for the
reasons I stated. I don't hack GNU Emacs[1], and AFAICT, most GNU Emacs
developpers don't hack Gnus. Yet, you explained that we should adhere to
their coding style.
>>> Beside yourself, nobody argued in favor of those "by-the-way
>>> whitespace changes".
>>
>> So what ? When I think the majority is wrong, I try to convince
>> the majority. Wouldn't you ?
>
> Note that this was a reply to...
>>>> Note that I will accept whatever decision the majority adopts
> ... so I tried to point out that the majority (at least of those who
> participated in the previous discussions) doesn't agree.
>
> [ You may even replace Emacs developers with Gnus developers in the
> paragraph above that upset you. ]
That's not necessarily true BTW, I think Yamaoka San was not as
strongly opposed as you are to my point of view.
But let me explain again: I was initially trying to convince the
Gnus committers. If I had failed, that would have been fine with me. But
then, you pointed out that it was not a matter of convincing the Gnus
Team, but the whole GNU Emacs team, and that, for the reason that we
should adhere to their coding style (which I consider illegitimate).
That's what upset me. Only that.
> _Not introducing_ trailing whitespace is different to "cleanup"
> leading spaces to tabs.
Hmmm. So we actually disagree on the kinds of whitespace cleanup
that should be authorized ? What about spaces followed by tabs ?
> If we'd agree that every Gnus developer should follows your proposal:
> How do you propose to ensure this?
By providing 4 lines of code for their .emacs.
>> OK, you made an illegitimate yet strong point.
>
> Making synchronization between v5-10 and the trunk as simple as
> possible is illegitimate?
I've clarified what I consider illegitimate a few paragraphs
above.
> But I don't think to accuse me of writing bullshit is good style.
There was nothing personal in what I said. You stated a fact
that upset me. It is the *fact* that you stated which upset me, not the
fact that you *stated* it. Err, do you see what I mean ? :-)
Footnotes:
[1] Actually, I did once: I rewrote rect.el for both Emacsen and then
they didn't report back the changes they made to it afterwards :-/
--
Read the Jazz Blog !! http://jazzblog.didierverna.com
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
next prev parent reply other threads:[~2007-04-19 7:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 19:05 Reiner Steib
2007-04-16 13:17 ` Didier Verna
2007-04-17 2:04 ` Katsumi Yamaoka
2007-04-17 7:14 ` Didier Verna
2007-04-17 8:05 ` Katsumi Yamaoka
2007-04-17 9:32 ` Didier Verna
2007-04-17 9:39 ` Didier Verna
2007-04-17 10:21 ` Katsumi Yamaoka
2007-04-17 23:42 ` Miles Bader
2007-04-18 8:50 ` Didier Verna
2007-04-18 9:15 ` Miles Bader
2007-04-17 17:25 ` Reiner Steib
2007-04-18 7:42 ` Didier Verna
2007-04-18 9:54 ` Didier Verna
2007-04-18 20:55 ` Reiner Steib
2007-04-19 7:17 ` Didier Verna [this message]
2007-04-19 7:39 ` Miles Bader
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=mux8xco7s02.fsf@uzeb.lrde.epita.fr \
--to=didier@xemacs.org \
--cc=ding@gnus.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).