From: Christopher Larson <kergoth@gmail.com>
To: "alex.kanavin@gmail.com" <alex.kanavin@gmail.com>,
Joakim.Tjernlund@infinera.com
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 2/3] shadow: Add PW_SUBDIR
Date: Wed, 15 Nov 2023 09:28:33 -0700 [thread overview]
Message-ID: <caa2bef7-9da7-4daf-83b9-e5247dd615af@Spark> (raw)
In-Reply-To: <4d8c459ce91ac4071c77c352006d0272d30efc90.camel@infinera.com>
[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]
On Nov 15, 2023 at 7:09 AM -0700, Joakim Tjernlund via lists.openembedded.org <Joakim.Tjernlund=infinera.com@lists.openembedded.org>, wrote:
> On Wed, 2023-11-15 at 14:45 +0100, Alexander Kanavin wrote:
> > On Wed, 15 Nov 2023 at 14:42, Joakim Tjernlund
> > <Joakim.Tjernlund@infinera.com> wrote:
> > > > Pending... what exactly?
> > >
> > > Pending merge
> >
> > If a patch is pending merge, the correct status is 'Submitted' (with a
> > link). If it's already been merged, the correct status is 'Backport'
> > (also with a link). 'Pending' is a frowned-upon status used only when
> > there's a genuine obstacle to upstream submission.
>
> I had no idea, will stay away from Pending then. Thanks.
>
> >
> > > > In other words, upstream first, please. This is clearly not something
> > > > that oe-core should not be carrying and maintaining and rebasing.
> > >
> > > Upstream merged it, see https://github.com/shadow-maint/shadow/commit/ee3a79c6952f8ca649c286c7f76639d9d1dedaad
> >
> > You need to resubmit here with the correct upstream-status then.
> >
>
> Will do, I am just not sure on the overall patch submission procedure and what OW in general thinks.
https://docs.yoctoproject.org/contributor-guide/recipe-style-guide.html#patch-upstream-status in the new contributor guide covers it pretty well now.
--
Christopher Larson
chris_larson@mentor.com, chris.larson@siemens.com, kergoth@gmail.com
Principal Software Engineer, Embedded Linux Solutions, Siemens Digital Industries Software
[-- Attachment #2: Type: text/html, Size: 3089 bytes --]
next prev parent reply other threads:[~2023-11-15 16:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 20:34 [PATCH 0/3] Add sub dir for passwd files Joakim Tjernlund
2023-11-14 20:34 ` [PATCH 1/3] base-passwd: Add PW_SUBDIR Joakim Tjernlund
2023-11-14 20:34 ` [PATCH 2/3] shadow: " Joakim Tjernlund
2023-11-15 12:35 ` [OE-core] " Alexander Kanavin
2023-11-15 13:42 ` Joakim Tjernlund
2023-11-15 13:45 ` Alexander Kanavin
2023-11-15 14:06 ` Joakim Tjernlund
2023-11-15 14:11 ` Alexander Kanavin
2023-11-15 16:28 ` Christopher Larson [this message]
2023-11-14 20:34 ` [PATCH 3/3] pseudo: " Joakim Tjernlund
2023-11-29 11:56 ` [OE-core] [PATCH 0/3] Add sub dir for passwd files Ross Burton
2023-11-29 12:14 ` Joakim Tjernlund
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=caa2bef7-9da7-4daf-83b9-e5247dd615af@Spark \
--to=kergoth@gmail.com \
--cc=Joakim.Tjernlund@infinera.com \
--cc=alex.kanavin@gmail.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