From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/4] add myself to DEVELOPERS
Date: Wed, 20 Mar 2019 23:41:52 +0100 [thread overview]
Message-ID: <714b9965-1fe2-c85c-d3f7-4c3ea2fca0e1@mind.be> (raw)
In-Reply-To: <20190315133033.5275-4-norbert.lange@andritz.com>
On 15/03/2019 14:30, Norbert Lange wrote:
> Signed-off-by: Norbert Lange <norbert.lange@andritz.com>
> ---
> DEVELOPERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/DEVELOPERS b/DEVELOPERS
> index 8a57cb2e23..ce0e9234d8 100644
> --- a/DEVELOPERS
> +++ b/DEVELOPERS
> @@ -1628,6 +1628,7 @@ F: package/tpm-tools/
> F: package/trousers/
>
> N: Norbert Lange <nolange79@gmail.com>
> +F: package/libfuse3/
Indent with tab.
Also, this should be squashed with the previous one (when a package is added,
to the DEVELOPERS entry right away).
Regards,
Arnout
> F: package/tcf-agent/
>
> N: Olaf Rempel <razzor@kopf-tisch.de>
>
next prev parent reply other threads:[~2019-03-20 22:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 13:30 [Buildroot] package/libfuse3: new package [V2] Norbert Lange
2019-03-15 13:30 ` [Buildroot] [PATCH v2 1/4] package/libfuse: Install udev rules and set permissions Norbert Lange
2019-03-20 22:31 ` Arnout Vandecappelle
2019-04-02 20:56 ` Peter Korsgaard
2019-04-05 20:34 ` Peter Korsgaard
2019-03-15 13:30 ` [Buildroot] [PATCH v2 2/4] package/libfuse3: new package Norbert Lange
2019-03-20 22:40 ` Arnout Vandecappelle
2019-03-15 13:30 ` [Buildroot] [PATCH v2 3/4] add myself to DEVELOPERS Norbert Lange
2019-03-20 22:41 ` Arnout Vandecappelle [this message]
2019-03-15 13:30 ` [Buildroot] [PATCH v2 4/4] package/libfuse: common files from libfuse3 are prefered Norbert Lange
2019-03-20 22:55 ` Arnout Vandecappelle
2019-03-25 21:12 ` Norbert Lange
2019-03-26 9:50 ` Arnout Vandecappelle
2019-03-26 17:45 ` Norbert Lange
2019-03-26 20:18 ` Arnout Vandecappelle
2019-03-28 20:28 ` Norbert Lange
2019-04-01 11:23 ` Arnout Vandecappelle
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=714b9965-1fe2-c85c-d3f7-4c3ea2fca0e1@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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.