mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] setlocalversion: only use tags actually on current branch
Date: Wed, 12 Dec 2018 15:53:28 +0100	[thread overview]
Message-ID: <20181212145328.zsuwntfjofnjv4vr@pengutronix.de> (raw)
In-Reply-To: <1544625345.6959.54.camel@diehl.com>

Hi,

On Wed, Dec 12, 2018 at 02:35:45PM +0000, Denis OSTERLAND wrote:
> Am Mittwoch, den 12.12.2018, 14:51 +0100 schrieb Michael Olbrich:
> > On Wed, Dec 12, 2018 at 09:14:52AM +0000, Denis OSTERLAND wrote:
> > > 
> > > Consider following situation:
> > > 
> > >                            tag C
> > >                              v
> > >                      A---B---C topic
> > >                     /         \
> > >                D---E---F---G---H master
> > >                    ^
> > >                  tag E
> > > 
> > > PTXDIST_BSP_AUTOVERSION at commit G will be E-2-gXXXX,
> > > but at commit H it will be C-3-gXXXX.
> > > With --first-parent it will be E-3-gXXXX.
> > > This is more intuitive result,
> > > especially when more than just one branch gets merged.
> > Nack. This only works with explicit merges. If multiple people update the
> > branch with git pull/push, then the first parent may not be the upstream
> > commit and the correct tag may be missed.
> I am not sure if I got the point here.
> 
> Is this your concern:
>                            tag C
>                              v
>                      A---B---C origin/master
>                     /         \
>                D---E---F---G---H master
> 
> and now when pushing master to origin C becomes invisible.

Exactly, and that is not acceptable in general.

> > In your example above consider 'C' the HEAD of the local master branch
> > before a pull/push. Then the first parent of 'H' is 'C'. And a if 'F' is
> > the tag, then it is ignored.
> The branches are equal, so of course yes.
> 
> If I got you right:
> 
>               tag C
>                 v
>         A---B---C---H topic
>        /           /
>   D---E---F-------G master
>           ^
>         tag F
> 
> At G it is F-1-gXXXX.
> At H it is C-3-gXXXX and C-1-gXXXX with --first-parent.
> 
> Seems to be correct behavior to me.

I'm not sure what your point is here.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2018-12-12 14:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12  9:14 Denis OSTERLAND
2018-12-12  9:47 ` Alexander Dahl
2018-12-12 13:51 ` Michael Olbrich
2018-12-12 14:35   ` Denis OSTERLAND
2018-12-12 14:53     ` Michael Olbrich [this message]
2018-12-12 15:32       ` Denis OSTERLAND
2018-12-13  7:29 ` Uwe Kleine-König
2018-12-13  7:56   ` Denis OSTERLAND
2018-12-13  9:37     ` Denis OSTERLAND

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=20181212145328.zsuwntfjofnjv4vr@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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