From: "Yann E. MORIN" <yann.morin.1998@free.fr>
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:57:04 +0200 [thread overview]
Message-ID: <ZilkEG6eEZ0DXztV@landeda> (raw)
In-Reply-To: <20240424175359.37025-1-thomas@devoogdt.com>
Thomas, All,
On 2024-04-24 19:53 +0200, Thomas Devoogdt spake thusly:
> Signed-off-by: Thomas Devoogdt <thomas@devoogdt.com>
Applied to master, thanks.
Do you think you could follow up with the suggestion in the last comment
in that thread:
https://github.com/buildroot/buildroot/pull/134#issuecomment-1718506664
For example https://github.com/marketplace/actions/close-pull-request to
automatically close PR and add comment advising users how to contribute
Regards,
Yann E. MORIN.
> ---
> .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!
> +
> --
> 2.34.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-04-24 19:57 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
2024-04-24 19:57 ` Yann E. MORIN [this message]
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=ZilkEG6eEZ0DXztV@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--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.