git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Re* How to generate pull-request with info of signed tag
Date: Mon, 19 Dec 2011 11:55:16 -0800	[thread overview]
Message-ID: <7vobv4mj4r.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <87iplch79e.fsf@linux.vnet.ibm.com> (Aneesh Kumar K. V.'s message of "Mon, 19 Dec 2011 21:40:37 +0530")

"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> writes:

> It would be nice to get the below working
>
> git fetch git-url tag remote-tag-name:local-namespace/tag-name

AFAIR "fetch tag $v" is a shorthand for "fetch refs/tags/$v:refs/tags/$"
invented back when Linus was the maintainer of Git. You can say

 $ git fetch $url refs/tags/remote-tag-name:refs/tags/whatever-tag-name-you-want

to rename their tag to whatever name in your local repository.

Come to think of it, the last patch I sent out on request pull was very
wrong.  The point of the recent change to allow you to pull this way
(notice the lack of "tag")

    $ git pull $url $signed_tag_name

is so that you do not have to contaminate your own ref namespace with tags
that are used to leave audit trails in the history graph.

> That way we can make sure before merging i can cut-paste that url and
> the local tag name i wish to store this to. And then do a git-merge.

  reply	other threads:[~2011-12-19 19:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16  6:35 How to generate pull-request with info of signed tag Aneesh Kumar K.V
2011-12-16 16:22 ` Junio C Hamano
2011-12-16 16:56 ` Re* " Junio C Hamano
2011-12-17 13:27   ` Aneesh Kumar K.V
2011-12-17 19:47     ` Junio C Hamano
2011-12-19 16:10       ` Aneesh Kumar K.V
2011-12-19 19:55         ` Junio C Hamano [this message]
2011-12-19 20:06           ` Junio C Hamano
2011-12-21  6:30             ` Aneesh Kumar K.V
2011-12-21  7:03               ` Junio C Hamano
2011-12-21 16:51                 ` Aneesh Kumar K.V
2011-12-21 18:39                   ` Junio C Hamano

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=7vobv4mj4r.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=git@vger.kernel.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 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).