[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170913220803.xvvqqpqiqrtxptlc@sirena.org.uk>
Date: Wed, 13 Sep 2017 15:08:03 -0700
From: Mark Brown <broonie@...nel.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Guenter Roeck <linux@...ck-us.net>, Tom Gall <tom.gall@...aro.org>,
LKML <linux-kernel@...r.kernel.org>,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
Shuah Khan <shuahkh@....samsung.com>, patches@...nelci.org,
Ben Hutchings <ben.hutchings@...ethink.co.uk>,
linux- stable <stable@...r.kernel.org>
Subject: Re: [PATCH 4.9 00/14] 4.9.50-stable review
On Wed, Sep 13, 2017 at 02:30:46PM -0700, Greg Kroah-Hartman wrote:
> On Wed, Sep 13, 2017 at 12:18:12PM -0700, Guenter Roeck wrote:
> > Yes. I don't recall if it is a direct --force or if you would have to
> > remove the original tag first (with git push <repo> :refs/tags/<tag>).
> Ah, but then if someone had pulled the old tag, they would have to
> delete it locally before they can pull in the new one. That's the main
> reason I'll not do this...
If there's going to be more than one version of a given -rc isn't that
going to confuse testing reports? I'm struggling to see the
circumstance where a tag would get replaced.
> Again, use the make command that we have just for this reason...
Not arguing with this though...
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists