From: Fraser Tweedale <frase@frase.id.au>
To: Thomas Rast <trast@inf.ethz.ch>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] documentation: fix asterisks in fetch-options
Date: Mon, 24 Jun 2013 21:42:03 +1000 [thread overview]
Message-ID: <20130624114202.GT2457@bacardi.hollandpark.frase.id.au> (raw)
In-Reply-To: <8761x33fny.fsf@linux-k42r.v.cablecom.net>
Right you are. I missed that; apologies for the noise.
Fraser
On Mon, Jun 24, 2013 at 01:35:13PM +0200, Thomas Rast wrote:
> Fraser Tweedale <frase@frase.id.au> writes:
>
> > diff --git a/Documentation/fetch-options.txt b/Documentation/fetch-options.txt
> > index 9cb6496..f2ac3bc 100644
> > --- a/Documentation/fetch-options.txt
> > +++ b/Documentation/fetch-options.txt
> > @@ -61,11 +61,12 @@ endif::git-pull[]
> > ifndef::git-pull[]
> > -t::
> > --tags::
> > - This is a short-hand for giving "refs/tags/*:refs/tags/*"
> > - refspec from the command line, to ask all tags to be fetched
> > - and stored locally. Because this acts as an explicit
> > - refspec, the default refspecs (configured with the
> > - remote.$name.fetch variable) are overridden and not used.
> > + This is a short-hand for giving
> > + "refs/tags/{asterisk}:refs/tags/{asterisk}" refspec from the
> > + command line, to ask all tags to be fetched and stored
> > + locally. Because this acts as an explicit refspec, the
> > + default refspecs (configured with the remote.$name.fetch
> > + variable) are overridden and not used.
>
> Wasn't this already fixed by 9eb4754 (fetch-options.txt: prevent a
> wildcard refspec from getting misformatted, 2013-06-07), currently in
> master?
>
> --
> Thomas Rast
> trast@{inf,student}.ethz.ch
prev parent reply other threads:[~2013-06-24 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 11:31 [PATCH] documentation: fix asterisks in fetch-options Fraser Tweedale
2013-06-24 11:35 ` Thomas Rast
2013-06-24 11:42 ` Fraser Tweedale [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130624114202.GT2457@bacardi.hollandpark.frase.id.au \
--to=frase@frase.id.au \
--cc=git@vger.kernel.org \
--cc=trast@inf.ethz.ch \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).