From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0 of 2 v2] Config.in: comments should have correct dependencies
Date: Mon, 11 Nov 2013 00:01:48 +0100 [thread overview]
Message-ID: <87fvr3c143.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <patchbomb.1383812675@argentina> (Thomas De Schampheleire's message of "Thu, 07 Nov 2013 09:24:35 +0100")
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:
> This patch is yet another part of my attempts to cleanup Config.in files.
> As indicated in the second patch, there is much more on my list.
> In v2, I incorporated small comments from Arnout and Samuel. I think this is
> ready to be merged now.
> These patches are typically big as they touch a lot of files, but
> splitting them up somehow looks odd to me too (there is no meaningful
> split). As long as the patch is not held for too long before being
> merged, I don't think it is a big problem.
> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Committed both, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-11-10 23:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 8:24 [Buildroot] [PATCH 0 of 2 v2] Config.in: comments should have correct dependencies Thomas De Schampheleire
2013-11-07 8:24 ` [Buildroot] [PATCH 1 of 2 v2] manual: clarify that Config.in " Thomas De Schampheleire
2013-11-07 10:43 ` Samuel Martin
2013-11-07 8:24 ` [Buildroot] [PATCH 2 of 2 v2] Config.in files: add missing dependencies to toolchain option comments Thomas De Schampheleire
2013-11-10 23:01 ` Peter Korsgaard [this message]
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=87fvr3c143.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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.