From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3 of 6 v2] linux: add support for custom Mercurial repository
Date: Tue, 13 Aug 2013 11:09:14 +0200 [thread overview]
Message-ID: <20130813110914.00c661dc@skate> (raw)
In-Reply-To: <52087CBD.10501@mind.be>
Dear Arnout Vandecappelle,
On Mon, 12 Aug 2013 08:12:13 +0200, Arnout Vandecappelle wrote:
> Given that string options can't be propagated from their legacy values,
> and since the name of an option isn't really that important, I'd keep
> the _GIT_ names for the mercurial options as well.
>
> If we do rename the option symbol names, then I would make sure that it
> is propagated:
>
> default BR2_LINUX_KERNEL_CUSTOM_GIT_REPO_URL if BR2_LINUX_KERNEL_CUSTOM_GIT_REPO_URL != ""
>
> + add a comment to the .legacy file so these hacks can be removed
> eventually.
Hum, I'm not sure how this articulates with the _WRAP mechanism that
patch 1/6 is proposing. If we do this:
default BR2_LINUX_KERNEL_CUSTOM_GIT_REPO_URL if BR2_LINUX_KERNEL_CUSTOM_GIT_REPO_URL != ""
then why would we need the _WRAP thing?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-08-13 9:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 7:22 [Buildroot] [PATCH 0 of 6 v2] linux/uboot: add support for custom Mercurial repositories Thomas De Schampheleire
2013-07-24 7:22 ` [Buildroot] [PATCH 1 of 6 v2] Config.in.legacy: update description Thomas De Schampheleire
2013-07-27 13:50 ` Thomas Petazzoni
2013-08-12 5:59 ` Arnout Vandecappelle
2013-08-13 16:31 ` Arnout Vandecappelle
2013-08-14 16:27 ` Thomas De Schampheleire
2013-07-24 7:22 ` [Buildroot] [PATCH 2 of 6 v2] linux: don't take HEAD as default for git repositories Thomas De Schampheleire
2013-08-12 6:02 ` Arnout Vandecappelle
2013-08-13 10:00 ` Thomas Petazzoni
2013-07-24 7:23 ` [Buildroot] [PATCH 3 of 6 v2] linux: add support for custom Mercurial repository Thomas De Schampheleire
2013-08-12 6:12 ` Arnout Vandecappelle
2013-08-12 10:54 ` Thomas De Schampheleire
2013-08-12 11:01 ` Arnout Vandecappelle
2013-08-13 9:09 ` Thomas Petazzoni [this message]
2013-08-13 16:30 ` Arnout Vandecappelle
2013-08-14 17:06 ` Thomas De Schampheleire
2013-08-17 8:13 ` Thomas De Schampheleire
2013-08-19 16:05 ` Arnout Vandecappelle
2013-08-20 8:36 ` Thomas De Schampheleire
2013-08-21 5:40 ` Arnout Vandecappelle
2013-08-27 12:29 ` Thomas De Schampheleire
2013-08-27 14:14 ` Thomas De Schampheleire
2013-07-24 7:23 ` [Buildroot] [PATCH 4 of 6 v2] u-boot: " Thomas De Schampheleire
2013-07-24 7:23 ` [Buildroot] [PATCH 5 of 6 v2] linux/uboot: line-up repository-related configuration options Thomas De Schampheleire
2013-07-24 7:23 ` [Buildroot] [PATCH 6 of 6 v2] linux: mention 3.x.y kernels in 'custom version' help Thomas De Schampheleire
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=20130813110914.00c661dc@skate \
--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 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.