All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@st.com>
To: Vijay Lakshminarayanan <laksvij@gmail.com>,
	Junio C Hamano <gitster@pobox.com>
Cc: "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, 7 Dec 2011 09:50:24 +0530	[thread overview]
Message-ID: <4EDEE988.2070902@st.com> (raw)
In-Reply-To: <87wra9und4.fsf@gmail.com>


Thanks guys. This whole session was new to me.

On 12/7/2011 7:58 AM, Vijay Lakshminarayanan wrote:
> Junio C Hamano <gitster@pobox.com> writes:
> 
>> > Vijay Lakshminarayanan <laksvij@gmail.com> writes:
>> >
>>> >> I've found 
>>> >>
>>> >> $ GIT_EDITOR=cat git commit --amend
>>> >>
>>> >> useful.
>> >
>> > Are you sure it is a cat?
> Yes.

This didn't worked for me. Got following error:

cat: unrecognized option `--amend'
Try `cat --help' for more information.
error: There was a problem with the editor 'cat git commit --amend'.
Please supply the message using either -m or -F option.
Could not commit staged changes.

>> > I almost always use
>> >
>> >     $ EDITOR=: git commit --amend

Even this didn't worked for me:

error: pathspec '.git/COMMIT_EDITMSG' did not match any file(s) known to git.
error: There was a problem with the editor 'git commit --amend'.
Please supply the message using either -m or -F option.
Could not commit staged changes.

Only "true" worked for me.

Probably, i have an older version of git (version 1.7.2.2)

One more thing. I couldn't get completely how this worked. Maybe any pointers to
earlier discussions.

The way i am testing it is:
- Stop after a commit in middle of rebase using "edit" or "e" option
- set EDITOR or GIT_EDITOR
- change files
- git add changed_files
- git rebase --continue

-- 
viresh

  reply	other threads:[~2011-12-07  4:20 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 [this message]
2011-12-07  4:53         ` Björn Steinbrink
2011-12-07  5:45           ` Viresh Kumar
2011-12-07 15:06             ` Vijay Lakshminarayanan
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=4EDEE988.2070902@st.com \
    --to=viresh.kumar@st.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=laksvij@gmail.com \
    --cc=shiraz.hashim@st.com \
    --cc=vipin.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.