All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mittal, Anuj" <anuj.mittal@intel.com>
To: "luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
	"marius.kriegerowski@gmail.com" <marius.kriegerowski@gmail.com>
Cc: "bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] [PATCH] scriptutils: fix style to be more PEP8 compliant
Date: Fri, 15 Apr 2022 05:00:26 +0000	[thread overview]
Message-ID: <21a09c414ff08dcb87f1b5a2c127069e9aacfe45.camel@intel.com> (raw)
In-Reply-To: <9418ABBB-4F3C-4062-860A-53068272E18A@gmail.com>

On Thu, 2022-04-14 at 20:21 +0200, Marius Kriegerowski wrote:
> 
> Thanks for the clarification! Phew, if only there was a repository
> where I could open a merge request just as I’m used to… ;)
> 
> Anyway, so just for me to get this right in the future: There is one
> repository named poky (https://git.yoctoproject.org/poky). If I patch
> something in the bitbake subdirectory, I send that patch to bitbake-
> devel. If I patch something in the any other subdirectory I send a
> patch to openembedded-core?
> Is there a place where all that info is aggregated like a table with
> left column repo/directory and right column mailing list?

Its explained here:

https://git.yoctoproject.org/poky/tree/meta-poky/README.poky.md

Thanks,

Anuj


  reply	other threads:[~2022-04-18 14:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 11:40 [PATCH] scriptutils: fix style to be more PEP8 compliant Marius Kriegerowski
2022-04-14 15:08 ` [bitbake-devel] " Luca Ceresoli
2022-04-14 18:21   ` Marius Kriegerowski
2022-04-15  5:00     ` Mittal, Anuj [this message]
2022-04-15 11:41       ` Marius Kriegerowski
  -- strict thread matches above, loose matches on Subject: below --
2022-04-13 14:19 Marius Kriegerowski
2022-04-14  9:12 ` [bitbake-devel] " Alexandre Belloni
2022-04-14 11:43   ` Marius Kriegerowski
2022-04-14 12:29     ` Quentin Schulz

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=21a09c414ff08dcb87f1b5a2c127069e9aacfe45.camel@intel.com \
    --to=anuj.mittal@intel.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=marius.kriegerowski@gmail.com \
    /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.