From: Michael Witten <mfwitten@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Anatol Pomozov <anatol.pomozov@gmail.com>,
git@vger.kernel.org, computerdruid@gmail.com
Subject: Re: [PATCH] Clarify that '--tags' fetches tags only
Date: Thu, 22 Sep 2011 02:07:59 +0000 [thread overview]
Message-ID: <CAMOZ1Bt6gGVd6QuRZduZ4mJ=eoZ9d7xK-WfwZ3G-+oswT0RN_Q@mail.gmail.com> (raw)
In-Reply-To: <CAMOZ1Bvxc+vcofb_KyeLS7Gy=KOtX1SKv72cXA2NtwgYCWA31A@mail.gmail.com>
On Thu, Sep 22, 2011 at 02:01, Michael Witten <mfwitten@gmail.com> wrote:
> On Thu, Sep 22, 2011 at 00:49, Junio C Hamano <gitster@pobox.com> wrote:
>> --tags is merely a short-hand for "refs/tags/*:refs/tags/*")
>> explicitly from the command line
>
> [Disclaimer: I don't know the code or the semantics]
>
> Why not just use that explanation?
>
> This option is merely a short-hand for writing
> the refspec `refs/tags/*:refs/tags/*'; consequently,
> using this option overrides any default refspec that
> would be used if no refspec were provided on the
> command line. That is,
>
> git fetch --tags origin frotz
>
> is equivalent to:
>
> git fetch origin frotz 'refs/tags/*:refs/tags/*'
>
> In fact, if the command line parsing performed by `git fetch'
> is reasonably intelligent, then it might be worthwhile
> to relocate `--tags' in the example:
>
> That is,
>
> git fetch origin frotz --tags
>
> is equivalent to:
>
> git fetch origin frotz 'refs/tags/*:refs/tags/*'
>
Maybe this is less confusing for the example:
That is,
git fetch origin --tags
git fetch origin frotz --tags bar
are equivalent to:
git fetch origin 'refs/tags/*:refs/tags/*'
git fetch origin frotz 'refs/tags/*:refs/tags/*' bar
next prev parent reply other threads:[~2011-09-22 2:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 21:04 [PATCH] Clarify that '--tags' fetches tags only Anatol Pomozov
2011-09-02 21:18 ` Drew Northup
2011-09-21 23:52 ` Anatol Pomozov
2011-09-22 0:13 ` Michael Witten
2011-09-22 0:49 ` Junio C Hamano
2011-09-22 2:01 ` Michael Witten
2011-09-22 2:07 ` Michael Witten [this message]
2011-09-22 3:13 ` Andrew Ardill
2011-09-22 3:24 ` Michael Witten
2011-09-22 3:39 ` [PATCH] Docs: Clarify the --tags option of `git fetch' Michael Witten
2011-09-22 3:48 ` Michael Witten
2011-09-22 4:28 ` [PATCH] Clarify that '--tags' fetches tags only Junio C Hamano
2011-09-22 7:23 ` [PATCH v3] Docs: Clarify the --tags option of `git fetch' Michael Witten
2011-09-22 17:10 ` Junio C Hamano
2011-09-22 17:35 ` Michael Witten
2011-09-22 17:38 ` Michael Witten
2011-09-22 4:00 ` [PATCH] Clarify that '--tags' fetches tags only Junio C Hamano
2011-09-22 4:17 ` [PATCH v2] Docs: Clarify the --tags option of `git fetch' Michael Witten
2011-09-22 1:14 ` [PATCH] Clarify that '--tags' fetches tags only Daniel Johnson
2011-09-30 2:51 ` Peter Shenkin
2011-09-30 8:44 ` Jakub Narebski
2011-09-30 13:23 ` Michael Witten
2011-10-01 5:40 ` Peter Shenkin
2011-10-01 14:11 ` Michael Witten
2011-10-01 17:16 ` Peter Shenkin
2011-10-01 18:45 ` Michael Witten
2011-10-01 20:22 ` Peter Shenkin
2011-10-01 20:56 ` Michael Witten
2011-10-01 21:41 ` Peter Shenkin
2011-10-01 22:06 ` Peter Shenkin
2011-09-30 18:37 ` Junio C Hamano
2011-10-01 5:51 ` Peter Shenkin
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='CAMOZ1Bt6gGVd6QuRZduZ4mJ=eoZ9d7xK-WfwZ3G-+oswT0RN_Q@mail.gmail.com' \
--to=mfwitten@gmail.com \
--cc=anatol.pomozov@gmail.com \
--cc=computerdruid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.