From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Dario Binacchi <dariobin@libero.it>, buildroot@buildroot.org
Subject: Re: [Buildroot] [RESEND, 1/1] package/davinci-bootcount: new package
Date: Sat, 11 Dec 2021 11:02:44 +0100 [thread overview]
Message-ID: <20211211110244.657828c0@windsurf> (raw)
In-Reply-To: <5c132e20-a74d-8505-18f5-9935d8cbca8d@mind.be>
Hello Arnout,
On Sat, 11 Dec 2021 10:02:31 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:
> > package/Config.in | 1 +
> > package/davinci-bootcount/Config.in | 11 +++++++++++
> > package/davinci-bootcount/davinci-bootcount.hash | 2 ++
> > package/davinci-bootcount/davinci-bootcount.mk | 15 +++++++++++++++
>
> It would be nice to add yourself to the DEVELOPERS file [1] for this package.
I don't think it's "nice". To me, it is mandatory now to be added in
the DEVELOPERS file when contributing a new package. When I merge a
patch adding a new package, if the contributor has forgotten the entry
in the DEVELOPERS file, I always add it when applying.
> Please use two spaces between the columns in the hash file (this is something
> we haven't documented yet, unfortunately).
It is documented. See
https://buildroot.org/downloads/manual/manual.html#adding-packages-hash
in the Buildroot manual, which states:
The format of this file is one line for each file for which to check
the hash, each line with the following three fields separated by two
spaces:
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-12-11 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 17:53 [Buildroot] [RESEND,1/1] package/davinci-bootcount: new package Dario Binacchi via buildroot
2021-12-11 9:02 ` [Buildroot] [RESEND, 1/1] " Arnout Vandecappelle
2021-12-11 10:02 ` Thomas Petazzoni [this message]
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=20211211110244.657828c0@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=dariobin@libero.it \
/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