From: Chris Packham <judge.packham@gmail.com>
To: Jeremiah Mahler <jmmahler@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] wording fixes in the user manual and glossary
Date: Mon, 26 May 2014 19:50:15 +1200 [thread overview]
Message-ID: <5382F237.8070909@gmail.com> (raw)
In-Reply-To: <20140525083720.GA28739@hudson.localdomain>
On 25/05/14 20:37, Jeremiah Mahler wrote:
> On Sun, May 25, 2014 at 07:56:41PM +1200, Chris Packham wrote:
>> On 25/05/14 15:50, Jeremiah Mahler wrote:
>>> Some minor wording fixes in the user manual and glossary.
> ...
>>>
>>> -Eventually the developer cloned from will do additional work in her
>>> +Eventually the developer will do additional work in her cloned
>>> repository, creating new commits and advancing the branches to point
>>> at the new commits.
>>
>> I agree that the original wording isn't clear but I'm not sure the new
>> wording is any clearer. The paragraph is trying to explain how to fetch
>> upstream changes when they happen. My initial thought was to say
>> "Eventually the developer will do additional work in the upstream
>> repository" but perhaps it is to early to start throwing around terms
>> like upstream. Perhaps just saying "her repository" would be clearest.
>>
>
> The "developer cloned from will do" didn't sound right to me.
> But it sounds like my interpretation is not what you were trying to
> convey. I do like the "upstream" term, it helps describe the
> local/remote aspect.
>
> How about this:
>
> Eventually the upstream developer will do additional work in their
> repository. Creating new commits and advancing the branches to point
> at the new commits.
Sounds good to me.
>
> Then in the next paragraph it will discuss how to use `git fetch`
> to get these remote changes in to the local repository.
>
next prev parent reply other threads:[~2014-05-26 7:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 3:50 [PATCH] wording fixes in the user manual and glossary Jeremiah Mahler
2014-05-25 7:56 ` Chris Packham
2014-05-25 8:37 ` Jeremiah Mahler
2014-05-26 7:50 ` Chris Packham [this message]
2014-05-26 8:11 ` Ben Aveling
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=5382F237.8070909@gmail.com \
--to=judge.packham@gmail.com \
--cc=git@vger.kernel.org \
--cc=jmmahler@gmail.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).