From: Steve Dickson <SteveD@RedHat.com>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: nfs-utils tag
Date: Mon, 20 Jan 2020 10:52:28 -0500 [thread overview]
Message-ID: <1e71f70c-5ce1-9ba7-d3bc-8e96a30f2aa8@RedHat.com> (raw)
In-Reply-To: <d64033ad7277ce26e328d1b5c7b85050c201beb7.camel@hammerspace.com>
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
>
prev parent reply other threads:[~2020-01-20 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 14:43 nfs-utils tag Trond Myklebust
2020-01-20 15:52 ` Steve Dickson [this message]
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=1e71f70c-5ce1-9ba7-d3bc-8e96a30f2aa8@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@hammerspace.com \
/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;
as well as URLs for NNTP newsgroup(s).