From: Ben Aveling <bena.001@optusnet•com.au>
To: Chris Packham <judge.packham@gmail•com>,
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 18:11:43 +1000 [thread overview]
Message-ID: <5382F73F.2010704@optusnet.com.au> (raw)
In-Reply-To: <5382F237.8070909@gmail.com>
On 25/05/14 20:37, Jeremiah Mahler wrote:
>> 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.
>
The second sentence needs a verb. Maybe something along the lines of
"When they ${do_X}, ${Y} will happen" ?
Regards, Ben
prev parent reply other threads:[~2014-05-26 8:37 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
2014-05-26 8:11 ` Ben Aveling [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5382F73F.2010704@optusnet.com.au \
--to=bena.001@optusnet$(echo .)com.au \
--cc=git@vger$(echo .)kernel.org \
--cc=jmmahler@gmail$(echo .)com \
--cc=judge.packham@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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