From: Andreas Ericsson <ae@op5.se>
To: CJ van den Berg <cj@vdbonline.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH 07/11] git-fetch: Limit automated tag following to only fetched objects
Date: Sat, 10 Nov 2007 15:10:11 +0100 [thread overview]
Message-ID: <4735BBC3.5040207@op5.se> (raw)
In-Reply-To: <20071109121228.GA4241@prefect.vdbonline.net>
CJ van den Berg wrote:
> On Fri, Nov 09, 2007 at 06:06:31AM -0500, Shawn O. Pearce wrote:
>> We now redefine the rule to be: "tags are fetched if they refer
>> to an object that was just transferred; that is an object that is
>> new to your repository". This rule is quite simple to understand,
>> you only get a tag if you just got the object it refers to.
>
> With this new rule a retrospectively pushed tag will never be fetched,
> right? With our local work flow tags are only ever pushed retrospectively
> because the tagged commit has to first pass regression tests. So this would
> be a major regression for us.
>
Same for us. Deciding after something has been pushed that "ok, this version
works, let's make that one the release" is, I think, fairly common behaviour.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-11-10 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 11:06 [PATCH 07/11] git-fetch: Limit automated tag following to only fetched objects Shawn O. Pearce
2007-11-09 11:28 ` Johannes Sixt
2007-11-09 12:12 ` CJ van den Berg
2007-11-10 14:10 ` Andreas Ericsson [this message]
2007-11-09 22:26 ` Junio C Hamano
2007-11-11 5:49 ` Shawn O. Pearce
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=4735BBC3.5040207@op5.se \
--to=ae@op5.se \
--cc=cj@vdbonline.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.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.