From: Junio C Hamano <gitster@pobox•com>
To: Brandon Casey <casey@nrlssc•navy.mil>
Cc: Git Mailing List <git@vger•kernel.org>
Subject: Re: fetch <repo> <branch>:<branch> fetches tags?
Date: Mon, 28 Jan 2008 21:26:04 -0800 [thread overview]
Message-ID: <7vodb5qk2b.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7v3ashs5yg.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Mon, 28 Jan 2008 18:47:51 -0800")
Junio C Hamano <gitster@pobox•com> writes:
> Brandon Casey <casey@nrlssc•navy.mil> writes:
> ...
>> I expect these to _not_ fetch tags (and they don't):
>>
>> git fetch <repo> <branch>
>> git pull <repo> <branch>
>>
>> But, I did not expect these to fetch tags:
>>
>> git fetch <repo> <branch>:<branch>
>> git pull <repo> <branch>:<branch>
>
> Sigh... that matches my expectation.
>
> Did we break it when we overhauled "git fetch", or was this an
> independent "improvement" that happened long before that?
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.
It's just that the expectation you and I shared is the
documented behaviour everywhere, and we would need to document
the new behaviour.
next prev parent reply other threads:[~2008-01-29 5:26 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 [this message]
2008-01-29 8:46 ` Brandon Casey
2008-01-29 8:54 ` Junio C Hamano
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=7vodb5qk2b.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=casey@nrlssc$(echo .)navy.mil \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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