all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Patches with independent changes
Date: Fri, 24 Jan 2014 08:43:19 -0800	[thread overview]
Message-ID: <52E29827.7060209@cs.ucla.edu> (raw)
In-Reply-To: <83bnz1eo1x.fsf@gnu.org>

[retitling from "Changes in update-game-score.c"]

Eli Zaretskii wrote:

> chmod is documented to be able to return both negative and positive values

Really?  Where is it documented to do that?  It's not documented that 
way in the POSIX documentation for chmod, or in the Gnulib documentation 
of chmod porting hassles; see 
<http://pubs.opengroup.org/onlinepubs/9699919799/functions/chmod.html> 
and <http://www.gnu.org/software/gnulib/manual/html_node/chmod.html>, 
respectively.

Even if you're correct, which I doubt, trunk bzr 116116 would still be 
an example of what you're calling a "sumo" patch -- a patch containing 
multiple independent changes. One change addresses WINDOWSNT's lack of 
fchmod. Another addresses the perhaps-hypothetical issue that chmod can 
return positive values. So regardless, that patch does not follow the 
rule that patches should fix just one bug and should not make 
independent changes.

Insisting on such a rule would be silly, anyway. We don't follow that 
rule and we never have, and we shouldn't impose it now. Obviously there 
are advantages to putting independent changes in separate patches and in 
many cases we should do that, but an extremist insistence of this 
principle in all cases would significantly increase our maintenance 
burden for little or no benefit.




  parent reply	other threads:[~2014-01-24 16:43 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22 19:42 Changes in update-game-score.c Eli Zaretskii
2014-01-22 19:50 ` David Kastrup
2014-01-22 20:07   ` Eli Zaretskii
2014-01-22 20:10     ` David Kastrup
2014-01-23  1:51     ` Glenn Morris
2014-01-23  3:33       ` Paul Eggert
2014-01-23  3:53         ` Eli Zaretskii
2014-01-23 16:02           ` Eli Zaretskii
2014-01-23  3:58         ` Glenn Morris
2014-01-23  3:32 ` Paul Eggert
2014-01-23  3:52   ` Eli Zaretskii
2014-01-23  3:59     ` Glenn Morris
2014-01-23  4:30       ` Glenn Morris
2014-01-23  4:33         ` Glenn Morris
2014-01-23  4:56     ` Paul Eggert
2014-01-23 16:07       ` Eli Zaretskii
2014-01-23 18:18         ` Paul Eggert
2014-01-23 20:27         ` Juanma Barranquero
2014-01-23 21:50           ` Paul Eggert
2014-01-23 22:39             ` Juanma Barranquero
2014-01-24  7:34             ` Eli Zaretskii
2014-01-24  8:42               ` Paul Eggert
2014-01-24  9:17                 ` Eli Zaretskii
2014-01-24 15:29                   ` Jarek Czekalski
2014-01-24 15:40                     ` Eli Zaretskii
2014-01-24 15:42                     ` change the Subject line when you change topics [was: Changes in update-game-score.c] Drew Adams
2014-01-25 10:00                       ` Jarek Czekalski
2014-01-24 16:43                   ` Paul Eggert [this message]
2014-01-24 21:39                     ` Patches with independent changes Eli Zaretskii
2014-01-24 22:34                       ` Paul Eggert
2014-01-25  7:22                         ` Eli Zaretskii
2014-01-25 17:01                           ` Paul Eggert
2014-01-25 17:22                             ` Eli Zaretskii
2014-01-25 17:25                             ` Eli Zaretskii
2014-01-25 20:58                               ` Paul Eggert
2014-01-26  3:47                                 ` Eli Zaretskii
2014-01-26  7:41                                   ` Paul Eggert

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=52E29827.7060209@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.