From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Raphael Pavlidis <raphael.pavlidis@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/slirp4netns: new package
Date: Mon, 29 Aug 2022 21:48:28 +0200 [thread overview]
Message-ID: <20220829194828.GA3615594@scaer> (raw)
In-Reply-To: <553c9903-0b75-d35b-cd30-848a05168eb7@gmail.com>
Raphael, All,
On 2022-08-29 20:55 +0200, Raphael Pavlidis spake thusly:
> On 27.08.22 14:08, Yann E. MORIN wrote:
> >You forgot to add an entry in the DEVELOPERS file, and I forgot to
> >commit-amend my change, so I pushed a follow-up commit to add it.
> Thanks. I did not know that I have to add an entry to DEVELOPERS. So, the
> creator of the package have to be in the DEVELOPERS?
Yes, the idea is that, by submitting a package, you show an interest in
having that package work flawlessly in Buildroot.
Listing the package in DEVELOPERS will ensure that you are copied on the
build failures about that package, that the autobuilders [0] may uncover
when running the random configurations.
It also ensures that, should someone submit a change to that package,
you get listed by the utils/get-developers script, so they would put you
on Cc to the change, on the assumption that you know (at least a bit)
about the package.
[0] http://autobuild.buildroot.net/
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| 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:[~2022-08-29 19:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 17:50 [Buildroot] [PATCH 1/1] package/slirp4netns: new package Raphael Pavlidis via buildroot
2022-06-14 18:01 ` [Buildroot] [PATCH v2] " Raphael Pavlidis via buildroot
2022-08-27 10:57 ` Raphael Pavlidis via buildroot
2022-08-27 12:08 ` Yann E. MORIN
2022-08-29 18:55 ` Raphael Pavlidis
2022-08-29 19:48 ` Yann E. MORIN [this message]
2022-08-29 21:46 ` Thomas Petazzoni via buildroot
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=20220829194828.GA3615594@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=raphael.pavlidis@gmail.com \
--cc=thomas.petazzoni@bootlin.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.