git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: kalle <kalle@projektwerkstatt.de>
Cc: git@vger.kernel.org
Subject: Re: git help clone: questions
Date: Wed, 07 Mar 2018 14:45:34 -0800	[thread overview]
Message-ID: <xmqq4llrzer5.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <81c78c4f-b690-d06c-bb7d-9c65e33777b5@projektwerkstatt.de> (kalle@projektwerkstatt.de's message of "Wed, 7 Mar 2018 23:30:39 +0100")

kalle <kalle@projektwerkstatt.de> writes:

> Am 06.03.2018 um 02:36 schrieb Junio C Hamano:
>> kalle <kalle@projektwerkstatt.de> writes:
>> 
>>> -In the explanation of the option --reference: shouldn't there be
>>> written '<repository>' instead of  'reference repository'?
>> 
>> "Shouldn't X be Y?" is not an effective way to communicate; it
>> solicits a "no, the current one is fine." without any explanation.
>> 
>> If you think X should be Y for some reason, please say "I think X
>> should be Y BECAUSE Z" instead.  Without stating why you think
>> differently from what those who wrote the current text, it is hard
>> for people to respond either with "Yeah, you're right---I agree
>> with Z" or with "No, Z does not hold because..."
>> 
> I wrote this, because when it is written about 'reference repository', I
> consider it not totally clear, which repository is meant, as the option
> '--reference <repository>' only names one as <repository>.
> For reasons of clearness, I now propose writing "reference repository
> <repository>".

I do not have particularly a strong opinion, but I think it is very
sensible to call the value given to the option "--reference" with a
phrase that is not just "repository".

As the command line of "clone" must name one repository (i.e. the
one which we clone from), and its "--reference" option must name
another repository as its value (i.e. the one that we borrow from in
order to reduce the object transfer), calling both <repository>
makes it easier to confuse readers unless the writer carefully makes
sure that <repository> in the desription is unambiguous and it is
clear which one of these two repositories is being discussed by the
context.

I just re-read the existing Documentation/git-clone.txt and looked
for "reference".  All uses of "reference repository" in the prose
made sense and I found it would not be an improvement if any of them
is replaced with just "repository".  It may be helpful to add
something like:

	 --reference[-if-able] <repository>::
	+	Define a repository (reference repository) to borrow
	+	objects from.  
		If the reference repository is on the local machine,
		...

to define which repository we mean by that term, though.

  reply	other threads:[~2018-03-07 22:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05 23:10 git help clone: questions kalle
2018-03-06  1:36 ` Junio C Hamano
2018-03-07 22:30   ` kalle
2018-03-07 22:45     ` Junio C Hamano [this message]
2018-03-07 23:34       ` kalle

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=xmqq4llrzer5.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=kalle@projektwerkstatt.de \
    /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).