All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@st.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Cc: Shiraz HASHIM <shiraz.hashim@st.com>
Subject: Query on git commit amend
Date: Tue, 6 Dec 2011 13:53:00 +0530	[thread overview]
Message-ID: <4EDDD0E4.6040003@st.com> (raw)


Hello,

Suppose i want to add few new changes to my last commit (HEAD).
The way i do it is
$ git add all_changed_files
$ git commit --amend

OR
$ git commit --amend -a

With both these ways, i get a screen to edit the message too.

I want to know if there is a way to skip this screen.

i.e.
$ git commit --amend -a -some_other_option

which simply adds new changes to existing commit, without asking to change
message.

If there is no such way, then can we add a patch for this, if it looks a valid
case.

-- 
viresh

             reply	other threads:[~2011-12-06  8:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06  8:23 Viresh Kumar [this message]
2011-12-06  9:01 ` Query on git commit amend 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
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=4EDDD0E4.6040003@st.com \
    --to=viresh.kumar@st.com \
    --cc=git@vger.kernel.org \
    --cc=shiraz.hashim@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.