From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751427AbdINFen (ORCPT <rfc822;w@1wt.eu>);
        Thu, 14 Sep 2017 01:34:43 -0400
Received: from mail-pf0-f194.google.com ([209.85.192.194]:33403 "EHLO
        mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750770AbdINFek (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 14 Sep 2017 01:34:40 -0400
X-Google-Smtp-Source: ADKCNb7UE8xRV+xtWc8AWPK53MkMWRp8c1opU3guVV+KMIvCdbxrViR44NSBfnjb/Kr6U5An7kylQQ==
Date: Wed, 13 Sep 2017 22:34:37 -0700
From: Guenter Roeck <linux@roeck-us.net>
To: Willy Tarreau <w@1wt.eu>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Mark Brown <broonie@kernel.org>, Tom Gall <tom.gall@linaro.org>,
        LKML <linux-kernel@vger.kernel.org>, torvalds@linux-foundation.org,
        akpm@linux-foundation.org, Shuah Khan <shuahkh@osg.samsung.com>,
        patches@kernelci.org, Ben Hutchings <ben.hutchings@codethink.co.uk>,
        linux- stable <stable@vger.kernel.org>
Subject: Re: [PATCH 4.9 00/14] 4.9.50-stable review
Message-ID: <20170914053437.GA15810@roeck-us.net>
References: <20170912165253.709627159@linuxfoundation.org>
 <DE15C2BC-7EAB-48AD-8170-942E2C957451@linaro.org>
 <20170913034915.GA21161@kroah.com>
 <CAOfXc9HX7T_nYzFPmRT8yr2bsB6FL+xwScMotnnd_ptRmshvVg@mail.gmail.com>
 <20170913152213.GI27765@roeck-us.net>
 <20170913163655.nfdhr5gnl4sn4zsz@sirena.org.uk>
 <20170913185538.GA26390@kroah.com>
 <20170913191812.GA3478@roeck-us.net>
 <20170913213046.GE9288@kroah.com>
 <20170914021803.GA30154@1wt.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170914021803.GA30154@1wt.eu>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, Sep 14, 2017 at 04:18:03AM +0200, Willy Tarreau wrote:
> On Wed, Sep 13, 2017 at 02:30:46PM -0700, Greg Kroah-Hartman 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...
> 
> In fact not, the tags are automatically replaced upon pull. I've been
> using such a crappy workflow for some time in the past, sharing human
> errors with coworkers... Git is pretty tolerant to this. It's just
> that it's terribly confusing because you can then have two people with
> the same tag name pointing to different commit IDs, I really hate this,
> it only works when all users are in the same office and you shout
> "sorry I messed up, I'm pushing the tag again".
> 
> > Again, use the make command that we have just for this reason...
> 
> It also has the benefit of always reporting the same version for all
> users including those only downloading the -rc patch.
> 
It reports the same version, but it is not necessarily the same code.
There are cases where a rc is updated, but not the Makefile. That happens
quite a lot, actually. This is similar to mainline, which currently
claims to be v4.13.0 until -rc1, then it claims to be -rc1 until -rc2,
and so on.

Guenter