From: Franck Bui-Huu <vagabon.xyz@gmail.com>
Date: Mon, 10 Apr 2006 08:24:01 GMT
Subject: Re: git commit broken ?
Message-ID: <cda58cb80604100124k165307c3td84be984e607c6ae@mail.gmail.com>
In-Reply-To: <7vhd51alti.fsf@assigned-by-dhcp.cox.net>

2006/4/10, Junio C Hamano <junkio@cox.net>:
> "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...

oops, I forgot that switch, sorry for the noise.

Thanks
--
               Franck