From: Uwe Brauer <oub@mat•ucm.es>
To: git@vger•kernel.org
Subject: git log --graph with a sort of local revision number
Date: Thu, 15 Aug 2019 10:35:26 +0200 [thread overview]
Message-ID: <87blwq7rn5.fsf@mat.ucm.es> (raw)
Hi
I am an occasionally git user and am very used to local revision numbers
mercurial provides in its log command. I don't want to start the
discussion whether local revision numbers are useful or not, nor
whether mercurial is better or not.
I only want to know whether there is any possibility to have this number
in the log.
I have seen
https://stackoverflow.com/questions/4120001/what-is-the-git-equivalent-for-revision-number
That
git rev-list --count HEAD
But I would like to have it in the
git log --graph --decorate
So something like this
o changeset: 5:d3ae13222c31
| tag: tip
| user: Uwe Brauer <oub@mat•ucm.es>
| date: Wed Aug 14 14:23:29 2019 +0200
| summary: Six
|
o changeset: 4:64a3eee07e93
| user: Uwe Brauer <oub@mat•ucm.es>
| date: Wed Aug 14 14:23:28 2019 +0200
| summary: Fifth
Anybody know who to achieve it?
I presume
git checkout revnumber
Would not work?
I know that
git checkout HEAD~somenumber
Works
Uwe Brauer
next reply other threads:[~2019-08-15 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 8:35 Uwe Brauer [this message]
2019-08-18 19:00 ` git log --graph with a sort of local revision number Rafael Ascensão
2019-08-18 19:16 ` Uwe Brauer
2019-08-18 20:46 ` Uwe Brauer
2019-08-18 20:55 ` [SOLVED] (was: git log --graph with a sort of local revision number) Uwe Brauer
2019-08-20 14:32 ` [problem with name-rev] " Uwe Brauer
2019-08-20 15:06 ` SZEDER Gábor
2019-08-20 17:49 ` Rafael Ascensão
2019-08-20 18:21 ` [problem with name-rev] Junio C Hamano
2019-08-20 19:34 ` Uwe Brauer
2019-08-20 19:57 ` Phil Hord
2019-08-21 7:50 ` Uwe Brauer
2019-08-21 12:37 ` Uwe Brauer
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=87blwq7rn5.fsf@mat.ucm.es \
--to=oub@mat$(echo .)ucm.es \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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