Git development
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@ucw.cz>
To: Krzysiek Pawlik <krzysiek.pawlik@people.pl>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Ability to automaticaly push tags to remote repositories.
Date: Fri, 2 Jun 2006 22:58:36 +0200	[thread overview]
Message-ID: <20060602205836.GG10488@pasky.or.cz> (raw)
In-Reply-To: <442BD562.3030207@people.pl>

Dear diary, on Thu, Mar 30, 2006 at 02:56:02PM CEST, I got a letter
where Krzysiek Pawlik <krzysiek.pawlik@people.pl> said that...
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> - From `cg-push --long-help`:
> 
> - -t TAG::
>         Tells cg-push to also push the given tag. Note that in the
>         future, cg-push should push tags automatically. Also note
>         that even if you pass `cg-push` the '-t' arguments, your
>         HEAD is still pushed as well in addition to the tags.
> 
> One of possible ways of doing it is in attached patch. Comments,
> suggestions?

Well, this works properly only when you ever push to a single
repository, which many people don't. Besides, if you have two branches,
push branch A but tag a commit only on branch B, you will now be pushing
an invalid tag since the other end won't have the branch B and thus the
tagged commit.

A better way would be to use git-ls-remote --tags to get the list of
remote tags and compare that with the list of local tags, then push
those tags that tag commits on the branch we are pushing and the other
end does not have them.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
A person is just about as big as the things that make them angry.

      parent reply	other threads:[~2006-06-02 20:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-30 12:56 [PATCH] Ability to automaticaly push tags to remote repositories Krzysiek Pawlik
2006-03-30 14:18 ` Krzysiek Pawlik
2006-06-02 20:58 ` Petr Baudis [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=20060602205836.GG10488@pasky.or.cz \
    --to=pasky@ucw.cz \
    --cc=git@vger.kernel.org \
    --cc=krzysiek.pawlik@people.pl \
    /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