From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/python-aiohttp-security: new package
Date: Fri, 7 Dec 2018 09:46:19 +0100 [thread overview]
Message-ID: <20181207094619.0f4bf1cd@windsurf> (raw)
In-Reply-To: <CADvTj4p0RkurDDaBQ5J2HFTshr6zZ7zMyHYC43R34BTSfqO_TA@mail.gmail.com>
Hello James,
On Fri, 7 Dec 2018 01:16:34 -0700, James Hilliard wrote:
> These are all independent patches which shouldn't depend on each
> other, I have them all in separate branches.
One issue is that since they touch packages with very close names, all
of those patches will conflict on the DEVELOPERS file and
package/Config.in files. I.e, if I apply your patch on
package/python-aiohttp-session and then apply your patch on
package/python-aiohttp-security, the latter will fail.
Those conflicts are trivial, so we can resolve them when applying. But
it's nicer when there are no conflicts at all, and in this case,
posting as a series of patches, as suggested by Yegor, makes a lot of
sense.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-07 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 23:33 [Buildroot] [PATCH 1/1] package/python-aiohttp-security: new package james.hilliard1 at gmail.com
2018-12-07 8:05 ` Yegor Yefremov
2018-12-07 8:16 ` James Hilliard
2018-12-07 8:46 ` Thomas Petazzoni [this message]
2018-12-07 8:48 ` James Hilliard
2018-12-07 8:56 ` Yegor Yefremov
2018-12-07 8:59 ` Thomas Petazzoni
2018-12-07 9:13 ` James Hilliard
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=20181207094619.0f4bf1cd@windsurf \
--to=thomas.petazzoni@bootlin.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