From: "Marcin Niestrój" <m.niestroj@grinn-global.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] DEVELOPERS: add Marcin Niestroj for netdata
Date: Tue, 29 Oct 2019 21:25:32 +0100 [thread overview]
Message-ID: <87lft3padf.fsf@grinn-global.com> (raw)
In-Reply-To: <c6c7fc2c-177f-0811-4b54-7c26afb59ccd@mind.be>
Arnout Vandecappelle <arnout@mind.be> writes:
>
> These DEVELOPERS changes should be together with the patches adding the
> respective files.
>
> Only when you add yourself as a developer for an already existing package it
> should be a separate patch, because in that case the addition to DEVELOPERS will
> be backported to the stable branches. For new packages (or tests), they don't
> exist on the stable branches, so backporting makes no sense.
>
> I normally would have fixed that up while applying, but since Matt asked for
> changes, I thought you could include that as well.
This information will be helpful in future contribution, so thanks for
explaining!
--
Regards,
Marcin Niestr?j
next prev parent reply other threads:[~2019-10-29 20:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 16:14 [Buildroot] [PATCH 1/3] package/netdata: new package Marcin Niestroj
2019-10-28 16:14 ` [Buildroot] [PATCH 2/3] support/testing: add netdata test Marcin Niestroj
2019-10-28 22:21 ` Matthew Weber
2019-10-30 9:31 ` Marcin Niestrój
2019-10-30 9:54 ` [Buildroot] [External] " Matthew Weber
2019-10-30 12:19 ` Matthew Weber
2019-10-30 14:07 ` Matthew Weber
2019-10-28 16:14 ` [Buildroot] [PATCH 3/3] DEVELOPERS: add Marcin Niestroj for netdata Marcin Niestroj
2019-10-28 22:57 ` Arnout Vandecappelle
2019-10-29 20:25 ` Marcin Niestrój [this message]
2019-10-28 22:39 ` [Buildroot] [PATCH 1/3] package/netdata: new package Matthew Weber
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=87lft3padf.fsf@grinn-global.com \
--to=m.niestroj@grinn-global.com \
--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.