Re: release-notes could be clearer on git-fetch changes

From: Jan Engelhardt <jengelh@inai.de>
Date: Feb 20, 2014, 17:54 UTC
Message-ID: <alpine.LSU.2.11.1402201754370.11221@nerf08.vanv.qr>
In-Reply-To: <alpine.LSU.2.11.1402192356480.1491@nerf08.vanv.qr>

On Thu, 20 Feb 2014 12:06:17, Michael Haggerty wrote:

Show 11 quoted lines

>On 02/19/2014 11:58 PM, Jan Engelhardt wrote:
>> 
>> Looking at it from one more angle, `git fetch r --tags` and
>> `git push r --tags` is now no longer symmetric :(
>
>I'm glad you brought this up, because I didn't really think about
>whether "git push" would need changes parallel to those in "git fetch".
>
>I use "git push" in very conservative ways, so I don't know its ins and
>outs.  What scenarios do you find asymmetric?  Were they more symmetric
>before?

`git push r --tags` pushes only tags, and `git fetch r --tags` only fetched tags.

Starting from 1.9.0, `git fetch r --tags`, according to the release summary, changed to "tags and other things".

That's the asymmetric change I find. It is, as you say, undesirable to have `git push r --tags` push more than tags, which is why I am objecting (acknowledging it's after-the-fact) that the change to git-fetch was so-so.

A new option `git fetch r --only-tags` could remedy the hard-to-remember syntax `git fetch r "refs/tags/*:refs/tags/*"`, though it would not fix the asymmetry.