git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: layer <layer@known.net>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How can I tell if a tag has been pushed, or not?
Date: Fri, 10 Jul 2009 13:02:23 -0700	[thread overview]
Message-ID: <16198.1247256143@relay.known.net> (raw)
In-Reply-To: <81b0412b0907101228t2cc55aa6g21d2a11ec9caa1c1@mail.gmail.com>

Alex Riesen <raa.lkml@gmail.com> wrote:

>> On Fri, Jul 10, 2009 at 19:43, layer<layer@known.net> wrote:
>> > Here's the problem:
>> >
>> > I expect that users, in their own private repos, will from time to
>> > time create tags that should not be pushed.  Sometimes, tags that
>> > should be pushed will be created.
>> >
>> > I could require that the "public" tags follow a specific convention
>> > (start with "release", or something).  Then, the scripts all my
>> > developers use could use that and push only certain tags.  However,
>> > over time there could be a large number of them.  It seems undesirable
>> > to push each tag each time a push is done.  So, how can I tell if a
>> > tag has already been pushed?  Is there a way?
>> 
>> git push does not push any tags by default. You either have to
>> specify them explicitly or add --tags (all tags). Maybe that is enough?

No, I already knew about that.

>> Otherwise, there is always git ls-remote 'tags/*'...

This is what I needed.  Thanks.

  reply	other threads:[~2009-07-10 20:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-10 17:43 How can I tell if a tag has been pushed, or not? layer
2009-07-10 19:28 ` Alex Riesen
2009-07-10 20:02   ` layer [this message]
2009-07-11 13:44 ` Andreas Ericsson

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=16198.1247256143@relay.known.net \
    --to=layer@known.net \
    --cc=git@vger.kernel.org \
    --cc=raa.lkml@gmail.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).