From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: "Rafael Ascensão" <rafa.almas@gmail.com>,
git@vger.kernel.org, "Alban Gruin" <alban.gruin@gmail.com>
Subject: Re: [problem with name-rev] (was: git log --graph with a sort of local revision number)
Date: Tue, 20 Aug 2019 17:06:31 +0200 [thread overview]
Message-ID: <20190820150631.GW20404@szeder.dev> (raw)
In-Reply-To: <87pnkzkivn.fsf_-_@mat.ucm.es>
On Tue, Aug 20, 2019 at 04:32:12PM +0200, Uwe Brauer wrote:
> Here's what I get when I start committing on master, then switch to a
> branch foo and finally merge foo into master:
> * changeset: ae68dbe:master
> |\ user: Uwe Brauer
> | | date: Tue Aug 20 16:25:53 2019 +0200
> | | summary: 1.2.1/1.1
> | |
> | * changeset: c00bb5d:master^2
> | | user: Uwe Brauer
> | | date: Tue Aug 20 16:25:53 2019 +0200
> | | summary: 1.2.1
> | |
> | * changeset: 54c9230:master^2~1
> | | user: Uwe Brauer
> | | date: Tue Aug 20 16:25:53 2019 +0200
> | | summary: 1.2
> | |
> * | changeset: da0712f:master~1
> |/ user: Uwe Brauer
> | date: Tue Aug 20 16:25:53 2019 +0200
> | summary: 1.1
> |
> * changeset: 8eb999d:master~2
> user: Uwe Brauer
> date: Tue Aug 20 16:25:53 2019 +0200
> summary: 1
>
> That looks odd.
What exactly do you think looks odd? That "master^2~1", perhaps?
That's how commits on different branches are named, see 'man
gitrevisions', and 'git name-rev' works as designed.
next prev parent reply other threads:[~2019-08-20 15:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 8:35 git log --graph with a sort of local revision number Uwe Brauer
2019-08-18 19:00 ` 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 [this message]
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=20190820150631.GW20404@szeder.dev \
--to=szeder.dev@gmail.com \
--cc=alban.gruin@gmail.com \
--cc=git@vger.kernel.org \
--cc=oub@mat.ucm.es \
--cc=rafa.almas@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.