From: Junio C Hamano <gitster@pobox.com>
To: Brandon Casey <drafnel@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: fetch <repo> <branch>:<branch> fetches tags?
Date: Tue, 29 Jan 2008 00:54:42 -0800 [thread overview]
Message-ID: <7vabmpovu5.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <loom.20080129T055937-532@post.gmane.org> (Brandon Casey's message of "Tue, 29 Jan 2008 08:46:19 +0000 (UTC)")
Brandon Casey <drafnel@gmail.com> writes:
>> Having said that, I do not particularly think the new behaviour
>> is bad per-se. If you are storing what you fetched locally in
>> tracking branches, you are interested in their work enough to
>> want to auto-follow their tags.
>
> How is "tracking" defined? Is this a term that implies some configuration
> to link a local branch to a remote branch? Or is any local branch created
> from a remote branch considered "tracking"?
I probably should have said "Instead of just letting fetch
temporarily store the result in FETCH_HEAD and using it from
there, you saved it away; that's a good indication of you care
about it deeply enough".
It's really about what's convenient. I was somewhat upset that
the behaviour change was not I was very aware of (perhaps I said
it was a good idea and I then forgot), I didn't think the
earlier behaviour was broken, but if I have to choose, I think
the new behaviour is probably slightly nicer than the old one.
next prev parent reply other threads:[~2008-01-29 8:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 2:33 fetch <repo> <branch>:<branch> fetches tags? Brandon Casey
2008-01-29 2:41 ` Johannes Schindelin
2008-01-29 3:09 ` Brandon Casey
2008-01-29 2:47 ` Junio C Hamano
2008-01-29 4:19 ` Shawn O. Pearce
2008-01-29 5:26 ` Junio C Hamano
2008-01-29 8:46 ` Brandon Casey
2008-01-29 8:54 ` Junio C Hamano [this message]
2008-01-29 17:08 ` Brandon Casey
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=7vabmpovu5.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.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).