From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Johannes Sixt <j.sixt@eudaptics.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
msysgit@googlegroups.com, git@vger.kernel.org
Subject: Re: The msysGit Herald, issue 2
Date: Mon, 24 Sep 2007 17:32:12 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709241731510.28395@racer.site> (raw)
In-Reply-To: <46F7E2A5.6030202@eudaptics.com>
Hi,
On Mon, 24 Sep 2007, Johannes Sixt wrote:
> Linus Torvalds schrieb:
> >
> > 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?
>
> I don't think I fetched a tracking branch. If I do:
>
> $ mkdir foo && cd foo && git init
> $ git fetch ../git master:refs/heads/master
>
> (where ../git is a clone of git.git with a few local changes), I get all the
> tags. Good or bad?
The ":refs/heads/master" part says that you fetch into a tracking branch.
Ciao,
Dscho
next prev parent reply other threads:[~2007-09-24 16:33 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
2007-09-24 16:15 ` Johannes Sixt
2007-09-24 16:32 ` Johannes Schindelin [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0709241731510.28395@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=j.sixt@eudaptics.com \
--cc=msysgit@googlegroups.com \
--cc=torvalds@linux-foundation.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 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).