From: "Ping Yin" <pkufranky@gmail.com>
To: "Brandon Casey" <casey@nrlssc.navy.mil>
Cc: "Jakub Narebski" <jnareb@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git-rebase and reflog
Date: Thu, 1 May 2008 01:13:24 +0800 [thread overview]
Message-ID: <46dff0320804301013o17da30cg1fd847beca94ff58@mail.gmail.com> (raw)
In-Reply-To: <4818A6CA.5000409@nrlssc.navy.mil>
On Thu, May 1, 2008 at 1:05 AM, Brandon Casey <casey@nrlssc.navy.mil> wrote:
> Ping Yin wrote:
>
> > If your are right, how can i look over the branch reflog. I know the
> > master@{1} syntax, but i want to see master@{1}, master@{2} until
> > master@{n} in a single command just as how 'git reflog' shows HEAD@{1}
> > to HEAD@{n}.
>
> Have you checked the documentation for 'git reflog'?
>
> It says:
>
> The subcommand "show" (which is also the default, in the absence of any
> subcommands) will take all the normal log options, and show the log of
> the reference provided in the command-line (or `HEAD`, by default).
>
> So, 'git reflog show master' should get you what you want.
Oh, i missed that. Maybe we should add an example section.
>
> You may also want to check out the '-g' option to git-log. For example,
> 'git log -g master'.
Oh, wonderful.
However, i still think the intemediate commits of git-rebase needn't
go into HEAD's reflog because it's totally useless.
--
Ping Yin
next prev parent reply other threads:[~2008-04-30 17:14 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 [this message]
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=46dff0320804301013o17da30cg1fd847beca94ff58@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=jnareb@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