From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Large changesets
Date: Wed, 25 Feb 2015 11:02:38 -0300 [thread overview]
Message-ID: <54EDD5FE.2080908@zacarias.com.ar> (raw)
In-Reply-To: <20150224104300.GA24526@vostro>
On 02/24/2015 07:43 AM, Alex Suykov wrote:
> What's the best way to submit a relatively large patchset for review?
> Especially considering there may be v2, v3 etc.
>
> I'm working on some init-related stuff, and the first stage there is
> moving service file installation code (that's /etc/init.d/*, *.service)
> out of project .mk files and into pkg-generic.mk.
>
> So there's one patch that does pkg-generic changes, followed by one
> patch per package for each package that has service files, that's 70+
> patches already, a bit too much to post right away I think.
Hi.
Well, send it to the mailing list, the usual way here :)
If the changes to the packages are all of the same kind, for instance
because of infra move in the first patch or so you could send them all
together.
Something like "Convert package sysv initscripts to new format" and
another one of systemd service files.
Regards.
next prev parent reply other threads:[~2015-02-25 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 10:43 [Buildroot] Large changesets Alex Suykov
2015-02-25 14:02 ` Gustavo Zacarias [this message]
2015-02-26 10:48 ` Thomas Petazzoni
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=54EDD5FE.2080908@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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