From: David Kastrup <dak@gnu.org>
To: git@vger.kernel.org
Subject: Re: 1.5.3 plans and preparations
Date: Thu, 02 Aug 2007 11:42:37 +0200 [thread overview]
Message-ID: <868x8umfw2.fsf@lola.quinscape.zz> (raw)
In-Reply-To: Pine.LNX.4.64.0708021021060.14781@racer.site
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> On Thu, 2 Aug 2007, Junio C Hamano wrote:
>
>> - "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
prev parent reply other threads:[~2007-08-02 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 7:22 1.5.3 plans and preparations Junio C Hamano
2007-08-02 9:26 ` Johannes Schindelin
2007-08-02 9:42 ` David Kastrup [this message]
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=868x8umfw2.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=git@vger.kernel.org \
/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