On Fri, May 26, 2017 at 8:07 AM, Belisko Marek <[email protected]> wrote:
> On Fri, May 26, 2017 at 8:04 AM, Andrea Galbusera <[email protected]> > wrote: > > > > > > On Thu, May 25, 2017 at 10:44 PM, Belisko Marek <[email protected] > > > > wrote: > >> > >> Hi Robert, > >> > >> On Thu, May 25, 2017 at 10:38 PM, Robert P. J. Day > >> <[email protected]> wrote: > >> > On Thu, 25 May 2017, Belisko Marek wrote: > >> > > >> >> On Thu, May 25, 2017 at 9:10 PM, Robert P. J. Day > >> >> <[email protected]> wrote: > >> >> > > >> >> > is there some rationale for libgpiod.bb to be the lone recipe > >> >> > under meta-openembedded/meta? would that recipe not fit into some > >> >> > other layer? > >> > > >> >> I posted few days ago recipe for libgpiod. Please look at: > >> >> > >> >> http://lists.openembedded.org/pipermail/openembedded-devel/ > 2017-May/112810.html > >> > > >> > but that doesn't really answer the question as to why that recipe > >> > went into meta-openembedded/meta and not meta-openembedded/meta-oe. > >> > even the subject refers to "meta-oe", so why was that recipe placed in > >> > a directory named "meta"? was that perhaps a typo? > >> Yes probably type. First version of patch was placed in meta-oe. My > >> bad. I'll fix that but didn't get any feedback on patch yet. Thanks. > > > > > > Your patch was already merged with the 'suspicious' path. I'd suggest > > sending a new patch that moves it under meta-oe/. > Hmm thanks. I wasn't aware of that that it was already merged. Thanks > I'll post updated version. > ;-) Sometime happened to me also. The convention for meta-openembedded's is not to ack on the list for each patch that get merged. Keep an eye on your patchwork account or poll master-next and master branches to see where your patches are in the pipeline: useful to detect when they accidentally get stuck! -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
