git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@inai.de>
To: mhagger@alum.mit.edu
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: release-notes could be clearer on git-fetch changes
Date: Thu, 20 Feb 2014 18:54:34 +0100 (CET)	[thread overview]
Message-ID: <alpine.LSU.2.11.1402201754370.11221@nerf08.vanv.qr> (raw)
In-Reply-To: <alpine.LSU.2.11.1402192356480.1491@nerf08.vanv.qr>


On Thu, 20 Feb 2014 12:06:17, Michael Haggerty wrote:
>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.

      parent reply	other threads:[~2014-02-20 17:54 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
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 [this message]

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=alpine.LSU.2.11.1402201754370.11221@nerf08.vanv.qr \
    --to=jengelh@inai.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mhagger@alum.mit.edu \
    /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).