From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] efl: fix target package dependency on util-linux (libmount).
Date: Sat, 28 Jan 2017 21:45:21 +1300 [thread overview]
Message-ID: <20170128214521.21067f36@free-electrons.com> (raw)
In-Reply-To: <f3f89ca1-087c-239c-5e01-c47cab50e3b3@gmail.com>
Hello,
On Fri, 6 Jan 2017 00:20:55 +0100, Romain Naour wrote:
> > sounds good. Following that guideline I should add myself to that
> > file, likely in this patch. Okay?
>
> Well, It seems that the recommended way to do it is to send a separate patch.
> The reason is: if someone need to backport a patch adding a feature or a new
> package, we want to avoid a conflict in DEVELOPERS file while cherry-picking the
> commit.
>
> Thomas, can you confirm ?
Correct. Please send a separate patch.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-01-28 8:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 21:29 [Buildroot] [PATCH 0/2] efl: allow smaller builds Gustavo Sverzut Barbieri
2017-01-03 21:29 ` [Buildroot] [PATCH 1/2] efl: fix target package dependency on util-linux (libmount) Gustavo Sverzut Barbieri
2017-01-03 22:37 ` Romain Naour
2017-01-04 2:09 ` Gustavo Sverzut Barbieri
2017-01-05 23:20 ` Romain Naour
2017-01-06 12:42 ` Gustavo Sverzut Barbieri
2017-01-28 8:45 ` Thomas Petazzoni [this message]
2017-01-28 9:58 ` Thomas Petazzoni
2017-01-03 21:29 ` [Buildroot] [PATCH 2/2] efl: do not force dependency on libudev by making eeze a config option Gustavo Sverzut Barbieri
2017-01-03 22:20 ` Romain Naour
2017-01-04 1:10 ` Gustavo Sverzut Barbieri
2017-01-05 23:25 ` Romain Naour
2017-01-20 21:54 ` Romain Naour
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=20170128214521.21067f36@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox