All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCHv2] common_use_cases: add description of SOC_FAMILY
Date: Thu, 09 Sep 2010 18:19:15 +0200	[thread overview]
Message-ID: <1284049155.3948.54.camel@mattotaupa> (raw)
In-Reply-To: <131E5DFBE7373E4C8D813795A6AA7F080310BFAA0F@dlee06.ent.ti.com>

[-- Attachment #1: Type: text/plain, Size: 2326 bytes --]

Am Donnerstag, den 09.09.2010, 07:09 -0500 schrieb Maupin, Chase:
> > -----Original Message-----
> > From: openembedded-devel-bounces@lists.openembedded.org
> > [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
> > Paul Menzel
> > Sent: Wednesday, September 08, 2010 4:48 PM
> > To: openembedded-devel@lists.openembedded.org
> > Subject: Re: [oe] [PATCHv2] common_use_cases: add description of
> > SOC_FAMILY
> > 
> > Am Mittwoch, den 08.09.2010, 13:03 -0500 schrieb Chase Maupin:
> > > * Added a description of the SOC_FAMILY variable that
> > >   can be set in the machine configuration files.
> > >
> > > Signed-off-by: Chase Maupin <chase.maupin@ti.com>
> > > ---
> > >  docs/usermanual/chapters/common_use_cases.xml |   24
> > ++++++++++++++++++++++++
> > >  1 files changed, 24 insertions(+), 0 deletions(-)
> > >
> > > diff --git a/docs/usermanual/chapters/common_use_cases.xml
> > b/docs/usermanual/chapters/common_use_cases.xml
> > > index d86d0ca..ef81b95 100644
> > > --- a/docs/usermanual/chapters/common_use_cases.xml
> > > +++ b/docs/usermanual/chapters/common_use_cases.xml
> > > @@ -94,6 +94,30 @@ SRCDATE = "20061014"
> > >          </listitem>
> > >        </itemizedlist></para>
> > >
> > > +    <para>There are also some optional variables that can be defined:
> > > +    <itemizedlist>
> > > +    <listitem>
> > > +          <para><command>SOC_FAMILY</command> describes a family of processors
> > > +            that all share common features such as kernel versions,
> > > +            bootloaders, etc.  This is used to allow overrides for a whole
> > 
> > I think a full stop is required even if there is an abbreviation in
> > front of it. → etc..

> I'm afraid I don't understand what you are asking to have fixed.  Are you saying you want it to be etc.. instead of etc.
> 
> Just want to clarify before I remake this patch.

I verified it again and it looks like I am wrong and it is handled
differently in English than in German [1][2]. I am sorry for the noise.

[…]

> > Acked-by: Paul Menzel <paulepanter@users.sourceforge.net>

[…]


Thanks,

Paul


[1] https://secure.wikimedia.org/wikipedia/en/wiki/Full_stop#Abbreviations
[2] http://www.talktalk.co.uk/reference/dictionaries/english/data/d0082120.html

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2010-09-09 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 18:03 [PATCHv2] common_use_cases: add description of SOC_FAMILY Chase Maupin
2010-09-08 21:47 ` Paul Menzel
2010-09-09 12:09   ` Maupin, Chase
2010-09-09 16:19     ` Paul Menzel [this message]
2010-09-09  6:17 ` Frans Meulenbroeks
2010-09-10 19:01   ` Denys Dmytriyenko

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=1284049155.3948.54.camel@mattotaupa \
    --to=paulepanter@users.sourceforge.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.