From: Jakub Narebski <jnareb@gmail.com>
To: "Ping Yin" <pkufranky@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: git-rebase and reflog
Date: Wed, 30 Apr 2008 09:37:17 -0700 (PDT) [thread overview]
Message-ID: <m3d4o7nvt2.fsf@localhost.localdomain> (raw)
In-Reply-To: <46dff0320804300904i3402b5e7wf827f6759bc52901@mail.gmail.com>
"Ping Yin" <pkufranky@gmail.com> writes:
> The history of git-rebase will go into reflog. This kind of behaviour
> makes me annoyed when using git-reflog where i can see so many useless
> intermediate log entries (generated by rebase).
>
> So how about not recording the intermediate commits to reflog?
If I remember and understand it correctly, because currently rebase
uses detached HEAD, the intermediate steps would go into HEAD reflog,
but only final step would go into branch reflog...
Please correct me if I am wrong.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-04-30 16:38 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 [this message]
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
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=m3d4o7nvt2.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.