From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Jari Aalto <jari.aalto@cante.net>
Cc: git@vger.kernel.org, Drew Northup <drew.northup@maine.edu>
Subject: Re: [PATCH] git-add.txt: Order options alphabetically
Date: Thu, 2 Dec 2010 02:36:05 +0100 [thread overview]
Message-ID: <20101202013605.GA5221@neumann> (raw)
In-Reply-To: <8739qhuo09.fsf@picasso.cante.net>
Please don't cull Cc list.
Hi,
On Thu, Dec 02, 2010 at 12:28:06AM +0200, Jari Aalto wrote:
> 2010-12-01 21:45 Drew Northup <drew.northup@maine.edu>:
> > On Wed, 2010-12-01 at 21:29 +0200, Jari Aalto wrote:
> >
> >> 2010-12-01 20:53 Drew Northup <drew.northup@maine.edu>:
> >> > (lacking a commit message to tell me), WHY? [alphabetical]
> >>
> >> Quoting <http://permalink.gmane.org/gmane.comp.version-control.git/162552>
> >>
> >> - You read from top to bottom, therefore A-Z.
> >> - GNU project uses it in manual pages. It looks good, it looks
> >> professional, it looks clean. And it works when searching (= no
> >> oriantation problems regardless of tools; even when you print on
> >> paper when you don't have any computerized aids to help your search.).
> >>
> >> Jari
> >
> > THAT belongs in a commit message!!!
>
> It does not. No need to clutter 10's of message that long in there..
It definitely does.
People doing 'git log -- Documentation/git-add.txt' in the future will
want to see it, just as well as people doing 'git log --
Documentation/git-commit.txt', or 'git log --
Documentation/git-reset.txt', or ....
HtH,
Gábor
next prev parent reply other threads:[~2010-12-02 1:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 15:42 [PATCH] git-add.txt: Order options alphabetically jari.aalto
2010-12-01 18:53 ` Drew Northup
2010-12-01 19:27 ` Jari Aalto
2010-12-01 19:49 ` Drew Northup
2010-12-01 19:29 ` Jari Aalto
2010-12-01 19:45 ` Drew Northup
2010-12-01 22:28 ` Jari Aalto
2010-12-02 1:36 ` SZEDER Gábor [this message]
2010-12-01 22:04 ` Kevin Ballard
2010-12-01 22:30 ` Jari Aalto
2010-12-01 22:45 ` Kevin Ballard
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=20101202013605.GA5221@neumann \
--to=szeder@ira.uka.de \
--cc=drew.northup@maine.edu \
--cc=git@vger.kernel.org \
--cc=jari.aalto@cante.net \
/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 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.