From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Stephan Beyer <s-beyer@gmx.net>, Ariel <asgit@dsgml.com>,
git@vger.kernel.org
Subject: Re: git add -p with new file
Date: Tue, 13 Dec 2016 11:12:36 -0800 [thread overview]
Message-ID: <xmqqpokv3aor.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20161213185653.ys3ig377zhmblncl@sigill.intra.peff.net> (Jeff King's message of "Tue, 13 Dec 2016 13:56:53 -0500")
Jeff King <peff@peff.net> writes:
>> Perhaps the latter is not advertised well enough? "add -p" does not
>> even page so it is not very useful way to check what is being added
>> if you are adding a new file (unless you are doing a toy example to
>> add a 7-line file).
>
> I use "add -p" routinely for my final add-and-sanity-check,...
> ... To me they are all tools in the toolbox, and I can pick the one that
> works best in any given situation, or that I just feel like using that
> day.
Oh, there is no question about that. I was just pointing out that
"add -p" is not the "one that works best" when dealing with a path
that is not yet even in the index.
next prev parent reply other threads:[~2016-12-13 19:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 1:18 git add -p with new file Ariel
2016-12-07 9:22 ` Duy Nguyen
2016-12-09 18:26 ` Ariel
2016-12-12 20:24 ` Stephan Beyer
2016-12-09 14:11 ` Jeff King
2016-12-09 18:43 ` Ariel
2016-12-10 8:55 ` Jeff King
2016-12-10 22:04 ` Junio C Hamano
2016-12-11 13:00 ` Jeff King
2016-12-12 20:31 ` Stephan Beyer
2016-12-13 17:33 ` Jeff King
2016-12-13 18:48 ` Junio C Hamano
2016-12-13 18:56 ` Jeff King
2016-12-13 19:12 ` Junio C Hamano [this message]
2016-12-13 19:21 ` git add -p with unmerged files (was: git add -p with new file) Stephan Beyer
2016-12-13 19:49 ` Jeff King
2016-12-13 19:59 ` git add -p with unmerged files Junio C Hamano
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=xmqqpokv3aor.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=asgit@dsgml.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=s-beyer@gmx.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.