All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
	 Daiane Angolini <daiane.list@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [Documentation][PATCH] release-notes: grammar edits to introduction
Date: Tue, 20 Jan 2015 00:41:29 -0500	[thread overview]
Message-ID: <54BDEA89.4040604@mindchasers.com> (raw)
In-Reply-To: <CAP9ODKo5EZq+OQWrr-nL7PKYG5i3J=PEjni3Lnuqv4Pftsz3XA@mail.gmail.com>

On 01/16/2015 07:42 AM, Otavio Salvador wrote:
> On Fri, Jan 16, 2015 at 10:24 AM, Daiane Angolini <daiane.list@gmail.com> wrote:
>> On Fri, Jan 16, 2015 at 4:00 AM, Bob Cochran <yocto@mindchasers.com> wrote:
>>> Signed-off-by: Bob Cochran <yocto@mindchasers.com>
>>> -The BSP upstreaming cycle starts just after a |freescale_release_name|
>>> +The BSP upstream cycle starts just after a |freescale_release_name|
>>
>> Here I need Otavio's help.
>>
>> Otavio, I remember we have already discussed regarding the difference
>> of "upstreaming" and "upstream" but now I don't remember exactly what
>> =P
>>
>> I would say Bob's suggestion is ok, what do you think?
>
> As not being a native I mean have a wrong understand here. However I
> think we need to keep clear in the text that there is a flow of
> changes which _never_ ends, starting with the release.
>
> Bob, as a native, do you have a better idea?
>

I just submitted a V2 patch.  The title for the upstream section is now 
'upstreaming' in my attempt to concisely describe the act of submitting 
upstream patches.  However, I think the term 'upstream cycle' is also 
correct since 'upstream' describes the 'cycle', and cycle conveys that 
process never ends.

I hope I also addressed Daiane's other concerns adequately.

Thanks

Bob



      reply	other threads:[~2015-01-20  5:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16  6:00 [Documentation][PATCH] release-notes: grammar edits to introduction Bob Cochran
2015-01-16 12:24 ` Daiane Angolini
2015-01-16 12:42   ` Otavio Salvador
2015-01-20  5:41     ` Bob Cochran [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=54BDEA89.4040604@mindchasers.com \
    --to=yocto@mindchasers.com \
    --cc=daiane.list@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.