From: Vijay Lakshminarayanan <laksvij@gmail.com>
To: Viresh Kumar <viresh.kumar@st.com>
Cc: "Björn Steinbrink" <B.Steinbrink@gmx.de>,
"Junio C Hamano" <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
"Shiraz HASHIM" <shiraz.hashim@st.com>,
"Vipin KUMAR" <vipin.kumar@st.com>
Subject: Re: Query on git commit amend
Date: Wed, 07 Dec 2011 20:36:03 +0530 [thread overview]
Message-ID: <87ehwgv2uc.fsf@gmail.com> (raw)
In-Reply-To: <4EDEFD66.4020404@st.com> (Viresh Kumar's message of "Wed, 7 Dec 2011 11:15:10 +0530")
Viresh Kumar <viresh.kumar@st.com> writes:
[snip]
> Now, whats the benefit of
>
> GIT_EDITOR=cat git commit --amend
>
> over
>
> git commit --amend -C HEAD
>
> ?
The latter preserves the original timestamp of the commit and other
environment variables like GIT_COMMITTER_NAME GIT_COMMITTER_EMAIL
whereas GIT_EDITOR=cat (or true or :) are equivalent to opening up the
commit in an editor and so consider these variables during execution.
For instance, you could say
$ GIT_EDITOR=cat GIT_COMMITTER_EMAIL=foo@bar.baz git commit --amend
and the commiter email would be set to foo@bar.baz
--
Cheers
~vijay
Gnus should be more complicated.
next prev parent reply other threads:[~2011-12-07 15:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 8:23 Query on git commit amend Viresh Kumar
2011-12-06 9:01 ` Konstantin Khomoutov
2011-12-06 19:09 ` Dirk Süsserott
2011-12-06 9:11 ` Johannes Sixt
2011-12-06 9:20 ` Viresh Kumar
2011-12-06 9:22 ` Viresh Kumar
2011-12-06 15:46 ` Vijay Lakshminarayanan
2011-12-06 19:11 ` Jeff King
2011-12-07 2:18 ` Vijay Lakshminarayanan
2011-12-06 20:03 ` Junio C Hamano
2011-12-06 21:00 ` Junio C Hamano
2011-12-07 14:42 ` [PATCH/RFC 0/4] Re: commit: honor --no-edit Jonathan Nieder
2011-12-07 14:45 ` [PATCH 1/4] test: add missing "&&" after echo command Jonathan Nieder
2011-12-07 23:10 ` Jeff King
2011-12-07 23:11 ` Jeff King
2011-12-07 14:49 ` [PATCH 2/4] test: remove a porcelain test that hard-codes commit names Jonathan Nieder
2011-12-07 14:50 ` [PATCH 3/4] t7501 (commit): modernize style Jonathan Nieder
2011-12-07 14:54 ` [PATCH 4/4] test: commit --amend should honor --no-edit Jonathan Nieder
2011-12-07 2:28 ` Query on git commit amend Vijay Lakshminarayanan
2011-12-07 4:20 ` Viresh Kumar
2011-12-07 4:53 ` Björn Steinbrink
2011-12-07 5:45 ` Viresh Kumar
2011-12-07 15:06 ` Vijay Lakshminarayanan [this message]
2011-12-08 17:52 ` Junio C Hamano
2011-12-09 4:49 ` Viresh Kumar
2011-12-08 5:26 ` Viresh Kumar
2011-12-08 5:30 ` Viresh Kumar
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=87ehwgv2uc.fsf@gmail.com \
--to=laksvij@gmail.com \
--cc=B.Steinbrink@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=shiraz.hashim@st.com \
--cc=vipin.kumar@st.com \
--cc=viresh.kumar@st.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 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.