From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0 of 7] Introduction of kconfig-package infrastructure
Date: Wed, 30 Jul 2014 21:23:21 +0200 [thread overview]
Message-ID: <20140730212321.137e216b@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LV3P+qJGK11q9eGYtT+tJOMt4HGC3mou+86ch-PpVD64g@mail.gmail.com>
Thomas,
On Wed, 30 Jul 2014 19:58:48 +0200, Thomas De Schampheleire wrote:
> > Weird, you don't have the summary of patches in the cover letter. Don't
> > you use 'git --cover format-patch' to generate the cover letter?
>
> Is this a trick question? ;-)
Might be :-)
> I'm using mercurial to send out patches, unfortunately it does not
> have a ready-made option to get this summary of patches. I have wanted
> to do that in the past too, so I'll write a little script to mimic the
> output of git here.
You know, git is not *that* dangerous!
> > * Regarding the kconfig-package infra stuff, I'm mostly fine with it,
> > except for one detail: it pretends to be a package infrastructure,
> > but it is not. It is only a kind of "library" / "helper" to use next
> > to a real package infrastructure. And I think this is pretty
> > confusing considering the name that was chosen, and the way it works.
> >
> > My proposal would therefore be to turn it into a real package
> > infrastructure by simply making it inherit from generic-package,
> > much like autotools-package, cmake-package and al. All kconfig-based
> > packages are otherwise generic-package. I don't see the logic behind
> > using Kconfig for an autotools-based or cmake-based package, since
> > autotools and cmake are precisely here to provide configuration
> > capabilities that overlap with what kconfig provides. And as of
> > today, we have linux, barebox, uclibc and busybox, and all of these
> > use the generic-package infra.
>
> I never thought of it this way, but what you say makes perfect sense to me.
>
> >
> > I think it's really a minor change in the patches, and with this
> > change, I'm willing to merge this package infra.
>
> Great! I'm on it, hope to send out the adapted series soon...
Cool!
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-30 19:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 17:49 [Buildroot] [PATCH 0 of 7] Introduction of kconfig-package infrastructure Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 1 of 7] infra: introduce a " Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 2 of 7] uclibc: use $(MAKE) iso $(MAKE1) for menuconfig target Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 3 of 7] uclibc: convert to kconfig-package infrastructure Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 4 of 7] uclibc: only add kconfig targets if uclibc is enabled Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 5 of 7] busybox: convert to kconfig-package infrastructure Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 6 of 7] busybox: only add kconfig targets if uclibc is enabled Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 7 of 7] linux: remove support of linux26-* targets Thomas De Schampheleire
2014-07-29 21:52 ` [Buildroot] [PATCH 0 of 7] Introduction of kconfig-package infrastructure Thomas Petazzoni
2014-07-30 17:58 ` Thomas De Schampheleire
2014-07-30 19:23 ` Thomas Petazzoni [this message]
2014-07-30 20:01 ` Thomas De Schampheleire
2014-07-31 6:57 ` Jeremy Rosen
2014-07-31 8:03 ` Thomas De Schampheleire
2014-07-31 8:20 ` Jeremy Rosen
2014-07-31 12:54 ` Matthew Weber
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=20140730212321.137e216b@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