From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/6] support/gnuconfig: update to 2019-05-28
Date: Fri, 31 May 2019 23:02:14 +0200 [thread overview]
Message-ID: <878sumwd61.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190531145734.280f09b8@windsurf> (Thomas Petazzoni's message of "Fri, 31 May 2019 14:57:34 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
Hi,
> Overall, I am no longer so sure of the benefits vs. complexity
> trade-off here. The above issues can be resolved for sure, but is it
> worth it, compared to just having those two files in our tree ?
Indeed, lets drop that for now.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-05-31 21:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 20:34 [Buildroot] [PATCH v2 0/6] gnuconfig and csky updates Thomas Petazzoni
2019-05-28 20:34 ` [Buildroot] [PATCH v2 1/6] package/lmbench: use UPDATE_CONFIG_HOOK instead of CONFIG_UPDATE Thomas Petazzoni
2019-05-30 10:33 ` Peter Korsgaard
2019-05-28 20:34 ` [Buildroot] [PATCH v2 2/6] support/gnuconfig: update README.buildroot with reality Thomas Petazzoni
2019-05-30 10:34 ` Peter Korsgaard
2019-05-28 20:34 ` [Buildroot] [PATCH v2 3/6] support/gnuconfig: update to 2019-05-28 Thomas Petazzoni
2019-05-30 10:36 ` Peter Korsgaard
2019-05-30 12:38 ` Thomas Petazzoni
2019-05-30 12:53 ` Peter Korsgaard
2019-05-31 12:57 ` Thomas Petazzoni
2019-05-31 21:02 ` Peter Korsgaard [this message]
2019-05-31 20:04 ` Yann E. MORIN
2019-05-31 21:02 ` Thomas Petazzoni
2019-05-28 20:34 ` [Buildroot] [PATCH v2 4/6] toolchain/toolchain-external/toolchain-external-csky: new package Thomas Petazzoni
2019-05-29 5:48 ` Guo Ren
2019-05-29 6:49 ` Thomas Petazzoni
2019-05-28 20:34 ` [Buildroot] [PATCH v2 5/6] configs/csky_gx6605s: use the C-SKY external toolchain package Thomas Petazzoni
2019-05-28 20:34 ` [Buildroot] [PATCH v2 6/6] support/config-fragments/autobuild: add testing for the C-SKY architecture 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=878sumwd61.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.