From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Difference between v4.19.88-cip16-rebase..v4.19.88-cip16 was Re: Getting older -cip-rebase versions
Date: Fri, 10 Jan 2020 18:29:35 +0000 [thread overview]
Message-ID: <1e5e351b5d1811aef41983e78d02296597865f98.camel@codethink.co.uk> (raw)
In-Reply-To: <OSAPR01MB3667464CB9CF546447FDEEE9923E0@OSAPR01MB3667.jpnprd01.prod.outlook.com>
On Wed, 2020-01-08 at 04:02 +0000, nobuhiro1.iwamatsu at toshiba.co.jp wrote:
[...]
> > Any idea what is going on there? Which version is ok and which should
> > be adjusted?
>
> I already fixed these issue on local repository.
> Since first issue is on -rebase branch, I don't think it will have a big impact.
> Second issue is on cip branch, I will need to do force push and re-tag.
>
> Also, to avoid the same problem, I will add a step to check the differences when rebase and merge.
Anyone who has pulled the wrong tags already won't see updated tags.
So at this point I would suggest using new names for the fixed tags
(e.g. -rebase-2).
Maybe it is worthwhile to test in CI for the -rc repository that the
rebased branches match the corresponding non-rebased branches? (It is
probably not reasonable to require that this is true at other times.)
Ben.
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
next prev parent reply other threads:[~2020-01-10 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 17:25 [cip-dev] Getting older -cip-rebase versions Pavel Machek
2020-01-06 0:39 ` nobuhiro1.iwamatsu at toshiba.co.jp
2020-01-07 12:06 ` [cip-dev] Difference between v4.19.88-cip16-rebase..v4.19.88-cip16 was " Pavel Machek
2020-01-08 4:02 ` nobuhiro1.iwamatsu at toshiba.co.jp
2020-01-10 18:29 ` Ben Hutchings [this message]
2020-01-13 11:23 ` Chris Paterson
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=1e5e351b5d1811aef41983e78d02296597865f98.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/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.