From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
Yoann Congal <yoann.congal@smile.fr>
Cc: Yocto Mailing list <yocto@lists.yoctoproject.org>,
",openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [yocto] [OE-core] Yocto Project Status 11 Feb. 2025 (WW07)
Date: Thu, 13 Feb 2025 10:03:12 +0000 [thread overview]
Message-ID: <14a350e52c4e567fa995b08978b418fe1e43831e.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj_8qPoOjhR=uR_7WRZu0V0YdhbcN43fA6mbnQBU5198fw@mail.gmail.com>
On Thu, 2025-02-13 at 10:54 +0100, Alexander Kanavin wrote:
> On Thu, 13 Feb 2025 at 10:53, Yoann Congal <yoann.congal@smile.fr> wrote:
> > > > I don't think the github repo is going to work for either YP or OE
> > > > since there are repositories in both that use pull requests and we
> > > > can't have a one size fits all message. I think that means we would
> > > > have to do this with a .github directory in the repos themselves.
>
> > That would mean to create a ".github/" directory in those. Are we ready
> > to do this?
>
> I think so. RP pretty much confirmed this just above?
I said that it was probably the only viable way we've seen so far. I'm
not happy at the idea. I've not said "yes we should" as yet.
I'm wondering if we should set up that default repo saying "no pull
requests" then ask repos that do accept them to override the message
with their own pull request file? The default repo is only used as a
fallback. Does an empty file do the right thing just to remove the
default message?
Cheers,
Richard
next prev parent reply other threads:[~2025-02-13 10:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 15:57 Yocto Project Status 11 Feb. 2025 (WW07) Stephen K Jolley
2025-02-11 18:42 ` [OE-core] " Alexander Kanavin
2025-02-11 23:36 ` Richard Purdie
2025-02-12 8:08 ` [yocto] " Yoann Congal
2025-02-12 9:38 ` Alexander Kanavin
2025-02-12 9:46 ` Richard Purdie
2025-02-12 9:51 ` Richard Purdie
2025-02-12 11:19 ` Yoann Congal
2025-02-12 23:03 ` Yoann Congal
2025-02-13 8:48 ` Alexander Kanavin
2025-02-13 9:18 ` Yoann Congal
2025-02-13 9:45 ` Richard Purdie
2025-02-13 9:50 ` Alexander Kanavin
2025-02-13 9:52 ` Yoann Congal
2025-02-13 9:54 ` Alexander Kanavin
2025-02-13 10:03 ` Richard Purdie [this message]
2025-02-13 10:09 ` Alexander Kanavin
2025-02-13 11:16 ` Yoann Congal
2025-02-13 19:13 ` Justin Bronder
2025-02-13 21:37 ` [OE-core] " Yoann Congal
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=14a350e52c4e567fa995b08978b418fe1e43831e.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yoann.congal@smile.fr \
--cc=yocto@lists.yoctoproject.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