From: "J. Neuschäfer via buildroot" <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1] .github: add a pull request warning that explains the mailing list workflow
Date: Wed, 24 Apr 2024 21:28:01 +0200 [thread overview]
Message-ID: <ZildQdJEo56gsRZr@probook> (raw)
In-Reply-To: <20240424175359.37025-1-thomas@devoogdt.com>
On Wed, Apr 24, 2024 at 07:53:59PM +0200, Thomas Devoogdt wrote:
> Signed-off-by: Thomas Devoogdt <thomas@devoogdt.com>
> ---
> .github/pull_request_template.md | 6 ++++++
> 1 file changed, 6 insertions(+)
> create mode 100644 .github/pull_request_template.md
>
> diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
> new file mode 100644
> index 0000000000..319e67d861
> --- /dev/null
> +++ b/.github/pull_request_template.md
> @@ -0,0 +1,6 @@
> +Please do not submit a Pull Request via GitHub. Buildroot makes use of a
> +[mailing list](http://lists.buildroot.org/mailman/listinfo/buildroot) for patch submission and review.
> +See [submitting your own patches](http://buildroot.org/manual.html#submitting-patches) for more info.
> +
> +Thanks for your help!
Good idea. It's always good to catch misunderstandings early. And it's
a shame that GitHub seems to insist that PRs are open on every repo…
Reviewed-by: J. Neuschäfer <j.neuschaefer@gmx.net>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-04-24 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 17:53 [Buildroot] [PATCH v1] .github: add a pull request warning that explains the mailing list workflow Thomas Devoogdt
2024-04-24 18:04 ` Thomas Devoogdt
2024-04-24 19:28 ` J. Neuschäfer via buildroot [this message]
2024-04-24 19:57 ` Yann E. MORIN
2024-05-07 16:10 ` Peter Korsgaard
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=ZildQdJEo56gsRZr@probook \
--to=buildroot@buildroot.org \
--cc=j.neuschaefer@gmx.net \
--cc=thomas.petazzoni@bootlin.com \
--cc=thomas@devoogdt.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.