From: Junio C Hamano <junkio@cox.net>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Make git-commit cleverer - have it figure out whether it needs -a automatically
Date: Fri, 01 Dec 2006 03:32:09 -0800 [thread overview]
Message-ID: <7v7ixbam2u.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7vd573amuy.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Fri, 01 Dec 2006 03:15:17 -0800")
Junio C Hamano <junkio@cox.net> writes:
> I think another exception should be needed. If the index does
> not match the working tree, it should not default to "-a".
>
> Otherwise,
I think there needs a bit of explanation and additional step
that happened here. This by the way is not a made-up example.
Everything, including the 20-minute away, were what happened
when I did the latest blame fix you saw a few days ago.
* I am still futzing with blame from time to time, and have
this change almost permanently in my working tree.
$ cat P.diff
diff --git a/builtin-blame.c b/builtin-blame.c
index dc3ffea..46ce45c 100644
--- a/builtin-blame.c
+++ b/builtin-blame.c
@@ -38,7 +38,7 @@ static int max_digits;
static int max_score_digits;
#ifndef DEBUG
-#define DEBUG 0
+#define DEBUG 1
#endif
* I also have the GIT-VERSION-GEN change in my working tree.
> I want to fix another thing in pickaxe.
>
> $ edit builtin-blame.c
>
* Of course I did tests here.
> My wife calls me. Away from desk for 20 minutes. Later I come
> back.
* And then reverted the DEBUG back to 0 in preparation for
"checking into the index"
$ edit builtin-blame.c
> $ git update-index builtin-pickaxe.c
* And then I reverted it back for later futing.
$ git apply P.diff ;# that is a permanent-temporary file.
>
> I am so used to that name and did not realize that typo, and I
> was not paying too much attention. My wife calls me again.
> Away from desk and back in 20 minutes.
>
> $ git commit -m 'git-blame: Another fix.'
>
> Oops.
* Oops here is not just that builtin-blame.c would have been
committed; I'd almost never do "commit -a" in this repository,
because it would take that "DEBUG 1" change _and_
GIT-VERSION-GEN change into the commit.
> So, please turn this "cleverness" off when the index does not
> match the working tree.
next prev parent reply other threads:[~2006-12-01 11:32 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 [this message]
2006-12-01 12:33 ` Andy Parkins
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=7v7ixbam2u.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=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).