All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: ryenus <ryenus@gmail.com>
Cc: "Jacob Keller" <jacob.keller@gmail.com>,
	"Jakub Narębski" <jnareb@gmail.com>, "Kevin Daudt" <me@ikke.info>,
	"Git mailing list" <git@vger.kernel.org>
Subject: Re: Notation for current branch?
Date: Tue, 30 Aug 2016 11:19:42 -0700	[thread overview]
Message-ID: <xmqqoa4a3yrl.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAKkAvaxyEMjASzfGTqt73AtW7ag-YfqN1yVLEhFreiU-UVdnkA@mail.gmail.com> (ryenus@gmail.com's message of "Wed, 31 Aug 2016 02:09:58 +0800")

ryenus <ryenus@gmail.com> writes:

> For now the best use case I can think of is with git-reflog, e.g.,
> the meaning of `git reflog HEAD` and `git reflog feature-branch`
> are quite different, even if I'm currently on the feature-branch,
> especially when I want to track the rebase histories (if any).

"git reflog" gives you the reflog of HEAD in numbered format
(HEAD@{1}, HEAD@{2}, etc.), and "git reflog HEAD@{now}" is an
interesting way to tell it "I want that same HEAD reflog but not in
numbered but in timed format).

"git reflog @{0}" and "git reflog @{now}" give you the reflog of the
current branch in these formats.


      reply	other threads:[~2016-08-30 18:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-28  9:58 Notation for current branch? ryenus
2016-08-28 10:51 ` Kevin Daudt
2016-08-28 13:56   ` Jakub Narębski
2016-08-29  6:39     ` Jacob Keller
2016-08-29 19:49       ` Junio C Hamano
2016-08-29 19:52         ` Jacob Keller
2016-09-01 15:51           ` ryenus
2016-08-30 18:09         ` ryenus
2016-08-30 18:19           ` Junio C Hamano [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=xmqqoa4a3yrl.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jacob.keller@gmail.com \
    --cc=jnareb@gmail.com \
    --cc=me@ikke.info \
    --cc=ryenus@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.