From: Konstantin Khomoutov <kostix@bswap.ru>
To: Junio C Hamano <gitster@pobox.com>
Cc: Konstantin Khomoutov <kostix@bswap.ru>,
Konstantin Kharlamov <hi-angel@yandex.ru>,
git@vger.kernel.org
Subject: Re: Any way to make git-log to enumerate commits?
Date: Thu, 6 Dec 2018 14:48:36 +0300 [thread overview]
Message-ID: <20181206114835.oro32chgf4qp2yqd@tigra> (raw)
In-Reply-To: <xmqqa7ljbimv.fsf@gitster-ct.c.googlers.com>
On Thu, Dec 06, 2018 at 09:31:36AM +0900, Junio C Hamano wrote:
> >> It would be great if git-log has a formatting option to insert an
> >> index of the current commit since HEAD.
> >>
> >> It would allow after quitting the git-log to immediately fire up "git
> >> rebase -i HEAD~index" instead of "git rebase -i
> >> go-copy-paste-this-long-number-id".
> >
> > This may have little sense in a general case as the history maintained
> > by Git is a graph, not a single line. Hence your prospective approach
> > would only work for cases like `git log` called with the
> > "--first-parent" command-line option.
>
> I do not see why the "name each rev relative to HEAD" formatting
> option cannot produce HEAD^2~2 etc.
>
> It would be similar to "git log | git name-rev --stdin" but I do not
> offhand recall if we had a way to tell name-rev to use only HEAD as
> the anchoring point.
My reading was that the OP explicitly wanted to just glance at a single
integer number and use it right away in a subsequent rebase command.
I mean, use one's own short memory instead of copying and pasting.
The way I decided to format the reference in my sketch script — using
HEAD~<n> — is just a byproduct of the fact I was aware both of the
"gitrevisions" manual page and the fact `git name-rev` exists (though I
regretfully was not aware it's able to process a stream of `git log`).
Hence while getting fancy names for revisions would be technically
correct but less error-prone for retyping from memory ;-)
next prev parent reply other threads:[~2018-12-06 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 14:22 Any way to make git-log to enumerate commits? Konstantin Kharlamov
2018-12-05 14:54 ` Konstantin Khomoutov
2018-12-05 15:31 ` Elijah Newren
2018-12-05 15:43 ` Andreas Schwab
2018-12-06 0:31 ` Junio C Hamano
2018-12-06 11:48 ` Konstantin Khomoutov [this message]
2018-12-07 0:12 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181206114835.oro32chgf4qp2yqd@tigra \
--to=kostix@bswap.ru \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hi-angel@yandex.ru \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).