All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Alexey I. Froloff" <raorn@altlinux.org>, git@vger.kernel.org
Subject: Re: most annoying thing in git-push
Date: Tue, 23 Jun 2009 01:12:56 -0700 (PDT)	[thread overview]
Message-ID: <m3fxdrxt16.fsf@localhost.localdomain> (raw)
In-Reply-To: <7vd48va3dd.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:
> "Alexey I. Froloff" <raorn@altlinux.org> writes:
> 
> > Is is possible to add such functionality to git-push, so it will
> > push tags that point at objects that were uploaded to the remote
> > repository?
[...]

> It however is entirely a different matter if it is a sensible thing to do.
> 
> Often, a fetch is made from a public distribution point, which by
> definition has only branches and tags that are meant for public
> consumption.  It makes sense to auto-follow tags by default.
> 
> On the other hand, a push is almost always made from a private working
> repository to a public distribution point, in order to update the latter
> with only refs and objects meant for public consumption.  A developer
> working in such a private working repository will use tags that are not
> meant for public consumption while developing, and pushing all tags that
> are reachable from the commits that are being pushed out to the public
> distribution point is not necessarily desirable, as it will push out many
> tags that are only private to the working repository.
> 
> It certainly is not a sensible default behaviour, even though it might be
> handy as an option for special cases.

Perhaps if "autofollowing" of tags was enabled only for 
annotated/signed tags?

-- 
Jakub Narebski
ShadeHawk on #git

  reply	other threads:[~2009-06-23  8:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 19:21 most annoying thing in git-push Alexey I. Froloff
2009-06-23  5:21 ` ZoltánFüzesi
2009-06-23  6:08 ` Junio C Hamano
2009-06-23  8:12   ` Jakub Narebski [this message]
2009-06-23 15:20   ` Alexey I. Froloff

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=m3fxdrxt16.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=raorn@altlinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.