From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] docs: update DEVELOPERS modification process
Date: Sun, 5 Nov 2017 09:55:44 +0100 [thread overview]
Message-ID: <20171105095544.2b045a56@windsurf> (raw)
In-Reply-To: <87y3nl2mt2.fsf@dell.be.48ers.dk>
Hello,
On Sun, 05 Nov 2017 08:43:05 +0100, Peter Korsgaard wrote:
> > However, I agree that doing the DEVELOPERS change in a patch just
> > modifying the package is perhaps not desirable. When adding a new
> > package, yes, definitely, the DEVELOPERS entry should be added as part
> > of the same patch. However, when a package is being modified, that's a
> > different story, and the package change should be in a separate patch
> > than the DEVELOPERS addition.
>
> I'm not sure it really matters much. A package change with a
> modification of DEVELOPERS would most likely be for a version bump of an
> unmaintained package where the person bumping wants to take over
> ownership, or similar.
>
> I don't think it is a problem to update DEVELOPERS together with the
> package in such cases, but keeping it separately is also fine.
Agreed.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-05 8:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 21:10 [Buildroot] [PATCH 1/1] docs: update DEVELOPERS modification process Joseph Kogut
2017-11-04 18:53 ` Baruch Siach
2017-11-04 22:14 ` Thomas Petazzoni
2017-11-05 6:07 ` Baruch Siach
2017-11-05 8:55 ` Thomas Petazzoni
2017-11-05 7:43 ` Peter Korsgaard
2017-11-05 8:55 ` Thomas Petazzoni [this message]
2017-11-05 20:14 ` 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=20171105095544.2b045a56@windsurf \
--to=thomas.petazzoni@free-electrons.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.