From: Junio C Hamano <gitster@pobox.com>
To: Jan Engelhardt <jengelh@inai.de>
Cc: git@vger.kernel.org
Subject: Re: release-notes could be clearer on git-fetch changes
Date: Wed, 19 Feb 2014 12:01:45 -0800 [thread overview]
Message-ID: <xmqqtxbu98ie.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1402191952070.31131@nerf08.vanv.qr> (Jan Engelhardt's message of "Wed, 19 Feb 2014 19:53:32 +0100 (CET)")
Jan Engelhardt <jengelh@inai.de> writes:
> The release notes for 1.9.0 read:
>
>> * The "--tags" option to "git fetch" no longer tells the command to
>> fetch _only_ the tags. It instead fetches tags _in addition to_
>> what are fetched by the same command line without the option.
>
> I think the release notes should also say -- like it was done
> extensively for git add -- how to get back the old
> behavior (perhaps through now-different commands).
Perhaps, but the release note is not a place to repeat what the
documentation already teaches---it primarily is to enumerate the
changed areas, to highlight the things users may want to look up in the
documentation, to give them a starting point.
You would do something like this, I would think:
git fetch $there 'refs/tags/*:refs/tags/*'
next prev parent reply other threads:[~2014-02-19 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 18:53 release-notes could be clearer on git-fetch changes Jan Engelhardt
2014-02-19 20:01 ` Junio C Hamano [this message]
2014-02-19 22:58 ` Jan Engelhardt
[not found] ` <CAPc5daUgs8cKNnXcdjLy+S7jGN8BnjNzF66HMSz8infmo9Ws3Q@mail.gmail.com>
2014-02-20 9:51 ` Jan Engelhardt
2014-02-20 11:06 ` Michael Haggerty
2014-02-20 17:54 ` Jan Engelhardt
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=xmqqtxbu98ie.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jengelh@inai.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.