From: Linus Torvalds <torvalds@linux-foundation.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: msysgit@googlegroups.com, git@vger.kernel.org
Subject: Re: The msysGit Herald, issue 2
Date: Mon, 24 Sep 2007 08:44:49 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0709240840310.3579@woody.linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0709232153230.28395@racer.site>
On Sun, 23 Sep 2007, Johannes Schindelin wrote:
>
> > 6) What was the most frustrating moment when working with Git?
>
> Just the other day, I wanted to fetch a set of changes from a public
> repo into my test repo in order to cherry-pick from them - and it
> automatically fetched all the tags. But, the heck, I don't want them tags
> here, just the commits. I just can't figure out how to avoid the automatic
> fetching of tags.
The way this was *supposed* to work is that if you are not fetching a
"tracking branch", it should not fetch any tags.
Maybe this got broken lately?
Or maybe you did fetch a tracking branch?
Anyway, I fetch stuff all the time, and if git were to fetch the tags too,
I'd be *really* unhappy. So either the people I work with are just good
people, or more likely it still works the way it's supposed to work: if
you just fetch into FETCH_HEAD (by explicitly giving the remote repository
name, and not using tracking branches), it should not fetch tags for you.
Linus
next prev parent reply other threads:[~2007-09-24 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 20:54 The msysGit Herald, issue 2 Johannes Schindelin
2007-09-24 2:48 ` Shawn O. Pearce
2007-09-24 15:44 ` Linus Torvalds [this message]
2007-09-24 16:15 ` Johannes Sixt
2007-09-24 16:32 ` Johannes Schindelin
2007-09-24 16:49 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.0.999.0709240840310.3579@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).