Received-SPF: pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: nfs-utils tag
To:     Trond Myklebust <trondmy@hammerspace.com>
Cc:     "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
References: <d64033ad7277ce26e328d1b5c7b85050c201beb7.camel@hammerspace.com>
From:   Steve Dickson <SteveD@RedHat.com>
Message-ID: <1e71f70c-5ce1-9ba7-d3bc-8e96a30f2aa8@RedHat.com>
Date:   Mon, 20 Jan 2020 10:52:28 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <d64033ad7277ce26e328d1b5c7b85050c201beb7.camel@hammerspace.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

Hey!

On 1/17/20 9:43 AM, Trond Myklebust wrote:
> Hi Steve
> 
> It looks like the nfs-utils-2-4-3-rc5 tag was modified after it was
> pushed out:
> 
> Fetching origin
> From git://git.linux-nfs.org/projects/steved/nfs-utils
>  ! [rejected]                  nfs-utils-2-4-3-rc5 -> nfs-utils-2-4-3-rc5  (would clobber existing tag)
> error: Could not fetch origin
> 
> 
> Was that intentional? I don't usually do a force-pull of the tags (and
> I suspect most other people do not either) so it is easy to miss that
> tag change.
Yes... I did update the tag... I was wondering if that would cause any problems. :-)

I'm always pushed out tags but I never publish them, like I've started.
I'll try to be a bit more careful in the future... 

steved.

> 
> Cheers
>   Trond
>