From: "Avery Pennarun" <apenwarr@gmail.com>
To: "Ping Yin" <pkufranky@gmail.com>
Cc: "Brandon Casey" <casey@nrlssc.navy.mil>,
"Jakub Narebski" <jnareb@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git-rebase and reflog
Date: Wed, 30 Apr 2008 13:22:34 -0400 [thread overview]
Message-ID: <32541b130804301022l3a072f2p47ccb5639cd8a24e@mail.gmail.com> (raw)
In-Reply-To: <46dff0320804301013o17da30cg1fd847beca94ff58@mail.gmail.com>
On 4/30/08, Ping Yin <pkufranky@gmail.com> wrote:
> However, i still think the intemediate commits of git-rebase needn't
> go into HEAD's reflog because it's totally useless.
I don't know, I can imagine a situation where I'm doing a rebase, I
get a conflict, I type the wrong command, and so I lose a bunch of my
intermediate work because I was an idiot. The reflog sounds like it
would be helpful here as much as anywhere.
Have fun,
Avery
next prev parent reply other threads:[~2008-04-30 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 16:04 git-rebase and reflog Ping Yin
2008-04-30 16:37 ` Jakub Narebski
2008-04-30 16:56 ` Ping Yin
2008-04-30 17:05 ` Brandon Casey
2008-04-30 17:13 ` Ping Yin
2008-04-30 17:22 ` Avery Pennarun [this message]
2008-04-30 17:34 ` Junio C Hamano
2008-04-30 17:38 ` Ping Yin
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=32541b130804301022l3a072f2p47ccb5639cd8a24e@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=pkufranky@gmail.com \
/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