From: Jonathan Nieder <jrnieder@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Mark Lodato" <lodatom@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð" <avarab@gmail.com>,
"Matthieu Moy" <Matthieu.Moy@grenoble-inp.fr>,
git@vger.kernel.org, "Jeff King" <peff@peff.net>,
"Scott Chacon" <schacon@gmail.com>,
"Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>,
"Jakub Narębski" <jnareb@gmail.com>,
"Johannes Schindelin" <johannes.schindelin@gmx.de>,
"Piotr Krukowiecki" <piotr.krukowiecki.news@gmail.com>
Subject: Re: [1.8.0] use 'stage' term consistently
Date: Sun, 20 May 2012 12:58:28 -0500 [thread overview]
Message-ID: <20120520175828.GB3000@burratino> (raw)
In-Reply-To: <CAMP44s2cGeQq3V=jS1Xjg-S0-rMyKS79XFN9yFm+4KxMo963OA@mail.gmail.com>
Felipe Contreras wrote:
> On Sat, May 19, 2012 at 8:00 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> The "index" file (see gitindex(5)) typically holds a snapshot of
>> the content of the working tree, and it is this snapshot that is
>> taken as the content of the next commit. Thus after making any
>> changes to the working directory, and before running the commit
>> command, you must use the add command to add any new or modified
>> files.
>
> I find this paragraph completely unnecessary. This is useless
> distraction; the user wants to know about 'git add', she doesn't need
> to know about the index, and we should hide it from her.
Ok. Have you seen the current git-add(1) manpage? Do you have
patches that improve it to avoid such useless background information
in a non-confusing way?
Jonathan
next prev parent reply other threads:[~2012-05-20 17:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 13:04 [1.8.0] use 'stage' term consistently Felipe Contreras
2012-05-05 16:52 ` Philip Oakley
2012-05-05 17:30 ` Felipe Contreras
2012-05-05 19:53 ` Philip Oakley
2012-05-06 9:53 ` Zbigniew Jędrzejewski-Szmek
2012-05-06 10:21 ` Jakub Narebski
2012-05-06 10:39 ` Matthieu Moy
2012-05-06 20:15 ` Felipe Contreras
2012-05-06 21:21 ` Jakub Narebski
2012-05-08 3:51 ` Junio C Hamano
2012-05-06 21:09 ` Felipe Contreras
2012-05-06 10:26 ` Matthieu Moy
2012-05-06 21:16 ` Felipe Contreras
2012-05-06 21:30 ` Ævar Arnfjörð Bjarmason
2012-05-07 17:52 ` Junio C Hamano
2012-05-07 20:05 ` Ævar Arnfjörð Bjarmason
2012-05-08 4:06 ` Junio C Hamano
2012-05-08 8:55 ` Ævar Arnfjörð Bjarmason
2012-05-08 14:53 ` Junio C Hamano
2012-05-09 13:10 ` Felipe Contreras
2012-05-09 17:25 ` Matthieu Moy
2012-05-19 0:50 ` Mark Lodato
2012-05-19 6:00 ` Jonathan Nieder
2012-05-19 6:32 ` Jonathan Nieder
2012-05-20 12:04 ` Felipe Contreras
2012-05-20 18:06 ` Jonathan Nieder
2012-05-19 10:14 ` Philip Oakley
2012-05-20 11:49 ` Felipe Contreras
2012-05-20 17:58 ` Jonathan Nieder [this message]
2012-05-20 21:11 ` Junio C Hamano
2012-05-21 1:12 ` Felipe Contreras
2012-05-21 1:32 ` Jonathan Nieder
2012-05-18 20:34 ` Thiago Farina
2012-05-08 14:01 ` Sebastien Douche
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=20120520175828.GB3000@burratino \
--to=jrnieder@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=avarab@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=johannes.schindelin@gmx.de \
--cc=lodatom@gmail.com \
--cc=paolo.ciarrocchi@gmail.com \
--cc=peff@peff.net \
--cc=piotr.krukowiecki.news@gmail.com \
--cc=schacon@gmail.com \
/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).