Re: git commit broken ?
- From
Junio C Hamano <junkio@cox.net>
- Date
- Apr 10, 2006, 08:15 UTC
- Message-ID
- <7vhd51alti.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <cda58cb80604100102p92e5258qf33a128f75f1b088@mail.gmail.com>
"Franck Bui-Huu" <vagabon.xyz@gmail.com> writes:
Show 9 quoted lines
> 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...