From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Make git-commit cleverer - have it figure out whether it needs -a automatically
Date: Fri, 1 Dec 2006 12:33:20 +0000 [thread overview]
Message-ID: <200612011233.21210.andyparkins@gmail.com> (raw)
In-Reply-To: <7vd573amuy.fsf@assigned-by-dhcp.cox.net>
On Friday 2006 December 01 11:15, Junio C Hamano wrote:
> I think another exception should be needed. If the index does
> not match the working tree, it should not default to "-a".
No problem: just don't apply the patch :-) What you've asked for leaves it as
a no-op.
This patch activates "-a" when the index equals HEAD. i.e. git-commit would
do nothing in this situation. If it is disabled when the index doesn't match
the working tree, then we're back to "do nothing". i.e. HEAD==index==working
tree.
> So, please turn this "cleverness" off when the index does not
> match the working tree.
How does that help you? You've updated the index manually, so the
automatic "-a" is already disabled. Without this patch you would still have
committed the wrong thing.
$ edit builtin-blame.c
$ git update-index builtin-pickaxe.c
$ git commit
What is that you would like to have happened at this point?
Andy
--
Dr Andy Parkins, M Eng (hons), MIEE
next prev parent reply other threads:[~2006-12-01 12:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 11:06 [PATCH] Make git-commit cleverer - have it figure out whether it needs -a automatically Andy Parkins
2006-12-01 11:15 ` Junio C Hamano
2006-12-01 11:32 ` Junio C Hamano
2006-12-01 12:33 ` Andy Parkins [this message]
2006-12-02 8:09 ` Junio C Hamano
2006-12-02 9:45 ` Carl Worth
2006-12-03 9:57 ` Andy Parkins
-- strict thread matches above, loose matches on Subject: below --
2006-11-30 13:13 [PATCH/RFC] " Jakub Narebski
2006-11-30 13:24 ` [PATCH] " Andy Parkins
2006-11-30 13:32 ` Nguyen Thai Ngoc Duy
2006-11-30 13:41 ` Jakub Narebski
2006-11-30 15:01 ` Andy Parkins
2006-11-30 15:43 ` Salikh Zakirov
2006-11-30 16:28 ` Jakub Narebski
2006-12-01 10:59 ` Andy Parkins
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=200612011233.21210.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.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.
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).