Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 0/3] rename packages/ to recipes/ per earlier	agreement
Date: Tue, 17 Mar 2009 15:59:01 -0400	[thread overview]
Message-ID: <20090317195901.GC15734@denix.org> (raw)
In-Reply-To: <871vswlybr.fsf@neumann.lab.ossystems.com.br>

On Tue, Mar 17, 2009 at 04:54:32PM -0300, Otavio Salvador wrote:
> Frans Meulenbroeks <fransmeulenbroeks@gmail.com> writes:
> 
> > 2009/3/17 Koen Kooi <k.kooi@student.utwente.nl>:
> >> On 17-03-09 00:32, Denys Dmytriyenko wrote:
> >>>
> >>> Renaming packages/ directory to recipes/, as one of the several structural
> >>> changes, was proposed by Koen[1] and agreed/approved by many. Since Koen
> >>> currently doesn't have time/ability to do the change, and some people are
> >>> too eager to wait any longer, he asked me to do it. Please ack/nack.
> >>>
> >>> [1] http://thread.gmane.org/gmane.comp.handhelds.openembedded/21326
> >>>
> >>> Denys Dmytriyenko (3):
> >>>   rename packages/ to recipes/ per earlier agreement
> >>>   recipes: fix hardcoded instances of packages/
> >>>   base.bbclass: fix base_get_scmbasepath() to look for recipes/ and
> >>>     fall back to packages/ while parsing BBFILES
> >>
> >> Acked-By: Koen Kooi <koen@openembedded.org>
> >>
> >> Now, if you use patchwork, these acks and SOBs get added to your patch
> >> automagically :)
> >>
> >> regards,
> >>
> >> Koen
> >>
> >>
> >> _______________________________________________
> >> Openembedded-devel mailing list
> >> Openembedded-devel@lists.openembedded.org
> >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >>
> > Acked-By: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
> 
> Acked-By: Otavio Salvador <otavio@ossystems.com.br>

Sorry, already commited. Thanks anyway!

-- 
Denys




  reply	other threads:[~2009-03-17 20:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 23:32 [PATCH 0/3] rename packages/ to recipes/ per earlier agreement Denys Dmytriyenko
2009-03-16 23:32 ` [PATCH 1/3] " Denys Dmytriyenko
2009-03-16 23:32 ` [PATCH 2/3] recipes: fix hardcoded instances of packages/ Denys Dmytriyenko
2009-03-17  2:45   ` Khem Raj
2009-03-16 23:32 ` [PATCH 3/3] base.bbclass: fix base_get_scmbasepath() to look for recipes/ and fall back to packages/ while parsing BBFILES Denys Dmytriyenko
2009-03-23  8:57   ` Otavio Salvador
2009-03-23 16:21     ` Denys Dmytriyenko
2009-03-23 18:04       ` Otavio Salvador
2009-03-23 18:12         ` Philip Balister
2009-03-16 23:32 ` Denys Dmytriyenko
2009-03-17  0:56 ` [PATCH 0/3] rename packages/ to recipes/ per earlier agreement Mike (mwester)
2009-03-17  1:25   ` Philip Balister
2009-03-17 19:26   ` Denys Dmytriyenko
2009-03-19  0:25     ` Theodore A. Roth
2009-03-19  2:01       ` Denys Dmytriyenko
2009-03-19  3:13         ` Denys Dmytriyenko
2009-03-19  7:22           ` Frans Meulenbroeks
2009-03-19 17:05             ` Theodore A. Roth
2009-03-19 20:33               ` Frans Meulenbroeks
2009-03-17 13:09 ` Marcin Juszkiewicz
2009-03-17 14:42 ` Koen Kooi
2009-03-17 17:19   ` Frans Meulenbroeks
2009-03-17 19:54     ` Otavio Salvador
2009-03-17 19:59       ` Denys Dmytriyenko [this message]
2009-03-17 19:29   ` 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=20090317195901.GC15734@denix.org \
    --to=denis@denix.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox