From: Jeff King <peff@peff.net>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: non-empty index with git commit -a
Date: Tue, 15 Feb 2011 21:36:46 -0500 [thread overview]
Message-ID: <20110216023645.GA7085@sigill.intra.peff.net> (raw)
In-Reply-To: <AANLkTi=5E8D0mwMDNuMdgZS69kOnKCfs=Q8X5bpcjnYF@mail.gmail.com>
On Tue, Feb 15, 2011 at 10:43:53PM +0000, Sverre Rabbelier wrote:
> Can we please fix this?
>
> $ hack hack hack
> $ git add -p # carefully add my changes
> $ git commit -am "Add feature foo"
> $ DAAAMN YOUUU FINGERS!!
>
> I remember bringing this up before, but I can't remember what the
> discussion ended up coming to.
How do you differentiate this from:
$ hack hack hack
$ git add -p ;# carefully add my changes
$ hack hack hack
$ git diff ;# ok, everything looks good
$ git commit -am "Add feature foo"
? IOW, I don't think git can know that you are making a mistake in your
case, since from its perspectives those same actions might be
reasonable. The real problem is that your intermediate index state is
never saved. Do we need an index reflog? :)
-Peff
next prev parent reply other threads:[~2011-02-16 2:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 22:43 non-empty index with git commit -a Sverre Rabbelier
2011-02-16 2:36 ` Jeff King [this message]
2011-02-16 3:20 ` Jonathan Nieder
2011-02-16 3:27 ` Jeff King
2011-02-16 8:18 ` Sverre Rabbelier
2011-02-16 8:29 ` Nguyen Thai Ngoc Duy
2011-02-16 8:44 ` Jonathan Nieder
2011-02-16 8:51 ` Jeff King
2011-02-16 9:52 ` Sverre Rabbelier
2011-02-16 9:54 ` Jeff King
2011-02-16 9:58 ` Sverre Rabbelier
2011-02-16 10:06 ` Jeff King
2011-02-16 14:41 ` Michael J Gruber
2011-02-16 19:29 ` Jeff King
2011-02-16 18:51 ` Junio C Hamano
2011-02-16 19:36 ` Jeff King
2011-02-16 19:55 ` Junio C Hamano
2011-02-16 19:59 ` Jeff King
2011-02-16 21:03 ` Jakub Narebski
2011-02-16 21:46 ` Junio C Hamano
2011-02-16 22:34 ` Jeff King
2011-02-16 10:28 ` Matthieu Moy
2011-02-16 19:48 ` Jeff King
2011-02-16 18:47 ` Junio C Hamano
2011-02-16 9:05 ` Matthieu Moy
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=20110216023645.GA7085@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=srabbelier@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).