From: Andreas Ericsson <ae@op5.se>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@osdl.org>,
git@vger.kernel.org, Jan Harkes <jaharkes@cs.cmu.edu>
Subject: Re: [PATCH] git-fetch: follow tag only when tracking remote branch.
Date: Wed, 22 Feb 2006 22:19:42 +0100 [thread overview]
Message-ID: <43FCD56E.5090804@op5.se> (raw)
In-Reply-To: <7vfymbm72x.fsf_-_@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Unless --no-tags flag was given, git-fetch tried to always
> follow remote tags that point at the commits we picked up.
>
> It is not very useful to pick up tags from remote unless storing
> the fetched branch head in a local tracking branch. This is
> especially true if the fetch is done to merge the remote branch
> into our current branch as one-shot basis (i.e. "please pull"),
> and is even harmful if the remote repository has many irrelevant
> tags.
>
> This proposed update disables the automated tag following unless
> we are storing the a fetched branch head in a local tracking
> branch.
>
> Signed-off-by: Junio C Hamano <junkio@cox.net>
>
> ---
>
> * Likes, dislikes?
>
Likes a lot. This is a Good Thing.
--
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:[~2006-02-22 21:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 19:38 How to not download objects more than needed? Radoslaw Szkodzinski
2006-02-21 21:13 ` sean
2006-02-21 21:13 ` sean
2006-02-22 0:42 ` Linus Torvalds
2006-02-22 1:13 ` Jan Harkes
2006-02-22 1:55 ` Junio C Hamano
2006-02-22 3:11 ` Jan Harkes
2006-02-22 3:22 ` Junio C Hamano
2006-02-22 21:12 ` [PATCH] git-fetch: follow tag only when tracking remote branch Junio C Hamano
2006-02-22 21:19 ` Andreas Ericsson [this message]
2006-02-21 21:32 ` How to not download objects more than needed? 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=43FCD56E.5090804@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=jaharkes@cs.cmu.edu \
--cc=junkio@cox.net \
--cc=torvalds@osdl.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.