Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: buildroot@busybox.net
Subject: [Buildroot] SCM management
Date: Tue, 29 Mar 2011 03:41:28 +0200	[thread overview]
Message-ID: <20110329014128.GO6466@game.jcrosoft.org> (raw)
In-Reply-To: <20110316163052.GA8006@game.jcrosoft.org>

Hi,

	ping

Best Regards,
J.
On 17:30 Wed 16 Mar     , Jean-Christophe PLAGNIOL-VILLARD wrote:
> Hi,
> 
> 	During my work on barebox and the kernel
> 	I modify Buildroot to get the source from my git or the mainline
> 	and found out that we remove the tree everytime and re-clone it
> 
> 	This is time consuming specialy in develeopment when you add new
> 	commit for other user which need to re-checkout your tree.
> 
> 	So I'd like to propose a new way to manage the trees
> 	we could do something like on gentoo
> 
> 	as example with git
> 	we clone a bare tre and store it in dl and do not remove it so if you
> 	need a new version of the tree you just need to fetch it and do not
> 	clone it again
> 
> 	For this purpose I would propose to manage the tree like this in dl
> 	for git as example
> 	builddir/fetch/git-src/${package}
> 
> 	for bzr
> 	builddir/fetch/bzr-src/${package}
> 
> 	and to simplify the scm I would like to propose the manage it not via
> 	makefile rules but via scripts
> 
> Best Regards,
> J.

  reply	other threads:[~2011-03-29  1:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 16:30 [Buildroot] SCM management Jean-Christophe PLAGNIOL-VILLARD
2011-03-29  1:41 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
     [not found] ` <AANLkTik7W8-NnFEgU+ibjeTjVO1HHqwd4RwGvngR7kBT@mail.gmail.com>
2011-03-30 16:54   ` Martin Hicks
     [not found]   ` <20110331100008.GF7420@game.jcrosoft.org>
2011-03-31 12:48     ` Martin Hicks

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=20110329014128.GO6466@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.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