Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: Denys Dmytriyenko <denys@ti.com>,
	OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] autoconf: fix mistakes in SUMMARY and DESCRIPTION
Date: Mon, 31 Jul 2017 13:48:32 -0400	[thread overview]
Message-ID: <20170731174832.GV26405@denix.org> (raw)
In-Reply-To: <CAJ86T=WdvrPzvz6325onhpMWxgdOz5weZ=hUSSVXo94NzoA7Cw@mail.gmail.com>

On Fri, Jul 28, 2017 at 04:47:40PM -0700, Andre McCurdy wrote:
> On Fri, Jul 28, 2017 at 1:26 PM, Denys Dmytriyenko <denis@denix.org> wrote:
> > From: Denys Dmytriyenko <denys@ti.com>
> >
> > Signed-off-by: Denys Dmytriyenko <denys@ti.com>
> > ---
> > v1 - procude -> produce
> > v2 - produce -> produces
> >
> >  meta/recipes-devtools/autoconf/autoconf.inc | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/meta/recipes-devtools/autoconf/autoconf.inc b/meta/recipes-devtools/autoconf/autoconf.inc
> > index f1b2dfc..17ee50f 100644
> > --- a/meta/recipes-devtools/autoconf/autoconf.inc
> > +++ b/meta/recipes-devtools/autoconf/autoconf.inc
> > @@ -1,5 +1,5 @@
> > -SUMMARY = "A GNU tool that procude shell scripts to automatically configure software"
> > -DESCRIPTION = "Autoconf is an extensible package of M4 macros that produce shell scripts to automatically \
> > +SUMMARY = "A GNU tool that produces shell scripts to automatically configure software"
> > +DESCRIPTION = "Autoconf is an extensible package of M4 macros that produces shell scripts to automatically \
> 
> The DESCRIPTION was correct originally (since it's the M4 macros which
> produce the shell scripts, not the extensible package).
> 
> https://www.gnu.org/software/autoconf/autoconf.html

Good thing Richard picked up v1 of the patch then! :)


> >  configure software source code packages. Autoconf creates a configuration script for a package from a template \
> >  file that lists the operating system features that the package can use, in the form of M4 macro calls."
> >  LICENSE = "GPLv3"
> > --
> > 2.7.4
> >
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> 


  reply	other threads:[~2017-07-31 17:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-28 20:26 [PATCH v2] autoconf: fix mistakes in SUMMARY and DESCRIPTION Denys Dmytriyenko
2017-07-28 23:47 ` Andre McCurdy
2017-07-31 17:48   ` Denys Dmytriyenko [this message]
2017-08-01 10:27     ` Richard Purdie

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=20170731174832.GV26405@denix.org \
    --to=denis@denix.org \
    --cc=armccurdy@gmail.com \
    --cc=denys@ti.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox