git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pete Wyckoff <pw@padd.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	Michael Schubert <mschub@elegosoft.com>,
	git@vger.kernel.org, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Subject: Re: [PATCH] Change "remote tracking" to "remote-tracking"
Date: Wed, 3 Jul 2013 18:43:36 -0400	[thread overview]
Message-ID: <20130703224336.GA3702@padd.com> (raw)
In-Reply-To: <7vy59ncrjk.fsf@alter.siamese.dyndns.org>

gitster@pobox.com wrote on Wed, 03 Jul 2013 13:33 -0700:
> Jonathan Nieder <jrnieder@gmail.com> writes:
> 
> > Michael Schubert wrote:
> >
> >> --- a/Documentation/git-p4.txt
> >> +++ b/Documentation/git-p4.txt
> >> @@ -180,7 +180,7 @@ subsequent 'sync' operations.
> >>  	Import changes into given branch.  If the branch starts with
> >>  	'refs/', it will be used as is.  Otherwise if it does not start
> >>  	with 'p4/', that prefix is added.  The branch is assumed to
> >> -	name a remote tracking, but this can be modified using
> >> +	name a remote-tracking, but this can be modified using
> >>  	'--import-local', or by giving a full ref name.  The default
> >>  	branch is 'master'.
> >
> > This is confusing both before and after the patch.  What is "a remote
> > tracking"?
> >
> > Perhaps:
> >
> > 	--branch <ref>::
> > 		Import changes into <ref> instead of refs/remotes/p4/master.
> > 		If <ref> starts with refs/, it is used as is.  Otherwise, if
> > 		it does not start with p4/, that prefix is added.
> > 	+
> > 	By default a <ref> not starting with refs/ is treated as the
> > 	name of a remote-tracking branch (under refs/remotes/).  This
> > 	behavior can be modified using the --import-local option.
> > 	+
> > 	The default <ref> is "master".
> >
> > The rest of the patch looks good.
> 
> Myy reading did hiccup at the same "remote-tracking" used as if it
> were a noun, and your rewritten version reads much better.

Yes, very clear and complete rewrite; thanks.  The final
paragraph is perhaps duplicative of the first sentence, but adds
clarity, so I'm happy as it stands.

Acked-by: Pete Wyckoff <pw@padd.com>

		-- Pete

  reply	other threads:[~2013-07-03 22:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03  9:12 [PATCH] Change "remote tracking" to "remote-tracking" Michael Schubert
2013-07-03 10:02 ` Johan Herland
2013-07-03 18:38 ` Jonathan Nieder
2013-07-03 20:33   ` Junio C Hamano
2013-07-03 22:43     ` Pete Wyckoff [this message]
2013-07-04  9:05   ` Michael Schubert

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=20130703224336.GA3702@padd.com \
    --to=pw@padd.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=mschub@elegosoft.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 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).