From: Junio C Hamano <junkio@cox.net>
To: "Franck Bui-Huu" <vagabon.xyz@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git commit broken ?
Date: Mon, 10 Apr 2006 01:15:05 -0700 [thread overview]
Message-ID: <7vhd51alti.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <cda58cb80604100102p92e5258qf33a128f75f1b088@mail.gmail.com> (Franck Bui-Huu's message of "Mon, 10 Apr 2006 10:02:44 +0200")
"Franck Bui-Huu" <vagabon.xyz@gmail.com> writes:
> It seems that "git commit -a -c ORIG_HEAD" command do not work as
> expected.
>
> $ git commit -a -c ORIG_HEAD
> $ git status
> nothing to commit
>
> So it seems that c has been commmited this time...Is it the expected
> behaviour ?
You said "git commit -a" to tell it to commit all your changes
in your working tree, using "-c ORIG_HEAD" which means "take the
commit log message and authorship information from that commit".
So I do not understand what else, other than both a and c
getting committed (hence subsequent "git status" to report
"nothing to commit'), you are expecting...
next prev parent reply other threads:[~2006-04-10 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 8:02 git commit broken ? Franck Bui-Huu
2006-04-10 8:15 ` Junio C Hamano [this message]
2006-04-10 8:24 ` Franck Bui-Huu
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=7vhd51alti.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=vagabon.xyz@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox