Thread (3 messages) flat view 3 messages, 3 authors, 2016-06-15

Re: 1.5.3 plans and preparations

From: David Kastrup <hidden>
Date: 2016-06-15 22:43:25

Johannes Schindelin [off-list ref] writes:
On Thu, 2 Aug 2007, Junio C Hamano wrote:
quoted
  - "git commit --amend" is now compatible with various message source
    options such as -m/-C/-c/-F.
Urgh.  That makes it much more easy for new users to shoot
themselves in the foot.  By "-C" and "-F" you do not even see the
runstatus anymore, since no editor was fired up.  Please say
something like "use with care", or "do not try this at home", too.
Hm?  How is that specific to "--amend"?  Isn't that just a consequence
of -m/-C/-F, regardless of whether one uses --amend or not?

When there are unmerged changes, --amend will not complete anyway.
And of course, if you got things wrong, you can always do another
--amend, so it is not like there is serious damage involved.

What do I overlook here?

And before you complain about not getting a copy by Email again: I
have to go via Gmane from my work account, since it will for some
unfathomable reason drop most of my mails (except those I use for
testing the problem) from this address.  It is manual work to add a
"Cc" header in this setup (which I often forget), and even then, I
doubt this copy will arrive at your place via mail (please tell me if
it does).

-- 
David Kastrup
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help