unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Base patch for bug #5975 (bookmarking from Gnus Article buffer).
Date: Wed, 14 Jul 2010 11:06:13 +0200	[thread overview]
Message-ID: <87oceabfga.fsf@tux.homenetwork> (raw)
In-Reply-To: <83oceaqx0z.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 14 Jul 2010 11:37:32 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
>> Date: Wed, 14 Jul 2010 10:29:11 +0200
>> 
>> if patch WORK and is basically correct and is accepted of course, why
>> not applying patch as it is and modifying as Emacs developpers like in
>> one or more little other commits.
>
> Because there's a pedagogical value for the contributors in having
> them fix their code according to review comments.

That's the case where contributor modify himself the code according to
diverse comments. I agree.

But i am speaking of the case where contributor's code is modified by Emacs
developers, in this case it is better (IMHO) to commit over the initial
patch, specially if Emacs developer misunderstand some part of code and
make wrong changes (That's not the case here Karl ;-)) it is easier to
find whats wrong instead of long discussion.
Generally contributor need to all rewrite, sometime long time further.
That is extra work for contributor and also Emacs developer. 
 
> In general, you learn better what you do yourself, rather than
> watching others do it for you.

Yes i agree completely.

-- 
Thierry Volpiatto
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997 



  reply	other threads:[~2010-07-14  9:06 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29 12:43 No answer on bugs Thierry Volpiatto
2010-06-29 13:12 ` Lennart Borgman
2010-06-29 13:54 ` Karl Fogel
2010-06-29 14:14   ` Thierry Volpiatto
2010-06-29 19:26   ` Tassilo Horn
2010-06-29 19:57     ` Thierry Volpiatto
2010-06-29 20:10       ` Tassilo Horn
2010-06-29 20:16         ` Thierry Volpiatto
2010-07-13 21:31           ` Base patch for bug #5975 (bookmarking from Gnus Article buffer) Karl Fogel
2010-07-13 21:41             ` Karl Fogel
2010-07-14  8:29               ` Thierry Volpiatto
2010-07-14  8:37                 ` Eli Zaretskii
2010-07-14  9:06                   ` Thierry Volpiatto [this message]
2010-07-14  9:42                     ` Eli Zaretskii
2010-07-14 10:07                       ` Thierry Volpiatto
2010-07-14 10:18                         ` Eli Zaretskii
2010-07-14 10:57                           ` Thierry Volpiatto
2010-07-14 15:32                 ` Karl Fogel
2010-07-13 23:30             ` Glenn Morris
2010-07-14  0:33               ` Karl Fogel
2010-07-14  8:55               ` Andreas Schwab
2010-07-14 15:29                 ` Karl Fogel
2010-07-14  5:03             ` Thierry Volpiatto
2010-07-14 16:06               ` Karl Fogel
2010-07-14 16:55                 ` Karl Fogel
2010-06-30 18:16 ` No answer on bugs Ted Zlatanov
2010-06-30 18:36   ` Thierry Volpiatto
2010-06-30 19:23     ` more on anything.el inclusion (was: No answer on bugs) Ted Zlatanov
2010-06-30 20:10       ` more on anything.el inclusion Thierry Volpiatto
2010-06-30 22:59         ` Dan Nicolaescu
2010-07-01  5:53           ` Thierry Volpiatto
2010-07-01  6:48             ` Dan Nicolaescu
2010-07-01  7:50               ` Thierry Volpiatto
2010-07-01  8:36                 ` Dan Nicolaescu
2010-07-01  8:53                   ` Thierry Volpiatto
2010-07-01 16:02                     ` Dan Nicolaescu
2010-07-01 16:33                       ` Harald Hanche-Olsen
2010-07-01 16:43                         ` Ted Zlatanov
2010-07-01 17:18                       ` Thierry Volpiatto
2010-07-01 17:43                         ` Dan Nicolaescu
2010-07-01 18:14                           ` Thierry Volpiatto
2010-07-01 18:48                           ` Ted Zlatanov
2010-07-01 18:57                           ` Wojciech Meyer
2010-07-01 17:36                       ` Harald Hanche-Olsen
2010-07-01 15:20                   ` Anything Use Case (was: more on anything.el inclusion) Memnon Anon
2010-07-01 13:18                 ` more on anything.el inclusion Ted Zlatanov
2010-07-01 14:15                   ` Thierry Volpiatto
2010-07-01 14:48                     ` Lennart Borgman
2010-07-01 15:55                     ` Ted Zlatanov
2010-07-01 16:43                       ` Lennart Borgman
2010-07-01 18:55                         ` Ted Zlatanov
2010-07-01 22:08                           ` Lennart Borgman
2010-07-09 14:46                       ` Thierry Volpiatto
2010-07-17 13:37                   ` rubikitch
2010-07-17 15:16                     ` Thierry Volpiatto
2010-07-04 22:02               ` Stefan Monnier
2010-07-07 16:47                 ` Ted Zlatanov
2010-07-23 15:35                   ` Stefan Monnier
2010-07-23 21:49                     ` rubikitch
2010-08-12 23:02                       ` Ted Zlatanov
2010-08-24 19:24                         ` rubikitch
2010-08-25 13:51                           ` Juri Linkov
2010-09-11 12:02                             ` Thierry Volpiatto
2010-09-11 11:59                           ` Thierry Volpiatto

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87oceabfga.fsf@tux.homenetwork \
    --to=thierry.volpiatto@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).