From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] git fetcher: do not remove the tree after initial clone
Date: Mon, 29 Aug 2011 14:23:44 +0200 [thread overview]
Message-ID: <20110829142344.2edcfd12@skate> (raw)
In-Reply-To: <4E5B445F.5050603@lucaceresoli.net>
Le Mon, 29 Aug 2011 09:48:47 +0200,
Luca Ceresoli <luca@lucaceresoli.net> a ?crit :
> Using BR for development has not been completely neglected anyway.
> Recently, Thomas Petazzoni submitted a patch that would allow to use a
> local directory to build the package. This is much different from using
> git fetches, but is expected to serve the "use BR for development" use
> case effectively.
> You might want to test it and comment to the author. Here it is:
> http://lists.busybox.net/pipermail/buildroot/2011-July/044479.html
I still think that this local directory mechanism is a better solution.
I have a new version of my patch set, which I hope to submit soon, at
least when the 2011.11 development process will open (by the end of the
month, so should be in the next few days).
Regards,
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:[~2011-08-29 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-28 13:32 [Buildroot] [PATCH] git fetcher: do not remove the tree after initial clone Nicolas Dechesne
2011-08-29 7:48 ` Luca Ceresoli
2011-08-29 12:23 ` Thomas Petazzoni [this message]
2011-08-29 14:59 ` Dechesne, Nicolas
2011-08-30 8:20 ` Luca Ceresoli
2011-08-30 8:43 ` Dechesne, Nicolas
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=20110829142344.2edcfd12@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.