From: Junio C Hamano <gitster@pobox.com>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: git@vger.kernel.org
Subject: Re: reflog weirdness
Date: Fri, 28 Dec 2007 16:06:36 -0800 [thread overview]
Message-ID: <7vprwqcqk3.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <87fxxme8x9.fsf@ambire.localdomain> (Thien-Thi Nguyen's message of "Fri, 28 Dec 2007 23:44:34 +0100")
Thien-Thi Nguyen <ttn@gnuvola.org> writes:
> () Junio C Hamano <gitster@pobox.com>
> () Fri, 28 Dec 2007 14:01:55 -0800
>
> Was it a buggy "git commit" command, or a bad commit log
> message was fed to "git commit" by the user, and there is
> nothing for me to worry about?
>
> i'm sorry, even though it was only a couple days ago, the actual
> events are far back in my memory, so i can't say. i wouldn't
> worry about it -- probably user error. (i'm new w/ git. most of
> the time i drive it from w/in emacs, which is well behaved; it is
> when i leave that comparative safety to do some flailing from the
> command-line that things go weird.)
>
> i suppose one way to improve git would be to test how it handles
> interruption (control-c in the middle of a commit, for example).
> a bit tricky to arrange (reproducibly), though...
>
> now i go search the docs for how to replace that log message.
"git-rebase -i"
next prev parent reply other threads:[~2007-12-29 0:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 19:57 reflog weirdness Thien-Thi Nguyen
2007-12-28 21:20 ` Junio C Hamano
2007-12-28 21:35 ` Thien-Thi Nguyen
2007-12-28 22:01 ` Junio C Hamano
2007-12-28 22:44 ` Thien-Thi Nguyen
2007-12-29 0:06 ` Junio C Hamano [this message]
2008-01-02 11:48 ` Thien-Thi Nguyen
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=7vprwqcqk3.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ttn@gnuvola.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;
as well as URLs for NNTP newsgroup(s).