From: Frans Pop <elendil@planet.nl>
To: Samuel Tardieu <sam@rfc1149.net>
Cc: John Feuerstein <john@feurix.com>, git@vger.kernel.org
Subject: Re: Feature request: option to not fetch tags for 'git remote' branches
Date: Tue, 30 Mar 2010 10:09:28 +0200 [thread overview]
Message-ID: <201003301009.29412.elendil@planet.nl> (raw)
In-Reply-To: <2010-03-27-20-10-25+trackit+sam@rfc1149.net>
On Saturday 27 March 2010, Samuel Tardieu wrote:
> Add a '--no-tags' option to 'git remote add' which adds a
> 'remote.REMOTE.tagopt = --no-tags' to the configuration file.
>
> 'git add -f -n REMOTE' will create a new remote and fetch from it
> without importing the tags. Subsequent 'git fetch REMOTE' will also
> not import the tags.
Not tested, but looks as if it will do exactly what I had in mind. Thanks!
prev parent reply other threads:[~2010-03-30 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 20:54 Feature request: option to not fetch tags for 'git remote' branches Frans Pop
2010-03-24 21:08 ` John Feuerstein
2010-03-24 21:35 ` Björn Steinbrink
2010-03-24 21:46 ` Frans Pop
2010-03-27 19:10 ` Samuel Tardieu
2010-03-27 19:25 ` Samuel Tardieu
2010-03-30 8:09 ` Frans Pop [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=201003301009.29412.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=git@vger.kernel.org \
--cc=john@feurix.com \
--cc=sam@rfc1149.net \
/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).