From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] support/download: fetch all refs on full git clone
Date: Mon, 16 Nov 2015 09:43:54 +0100 [thread overview]
Message-ID: <14498168.cEIkmZpZ53@sagittea> (raw)
In-Reply-To: <5645880C.5040103@mind.be>
Hello Arnout,
On Friday 13 November 2015 07:49:48 Arnout Vandecappelle wrote:
[...]
> What I
> think would make sense is that for distributed VCS downloads (i.e.
> git and hg) we keep a full (shallow) clone in DL_DIR in addition to
> the tarball. That makes handling updates a lot more efficient. We
> probably would want to expose that to PRIMARY and SECONDARY download
> sites as well. Especially the PRIMARY would be useful, since it would
> allow you to start from a local clone of e.g. linux.git (which may
> not have the ref you need), and then just fetch the missing refs from
> upstream.
>
> This will not be easy to implement, though, since we'd need to handle
> e.g. multiple remotes that end up in the same DL_DIR/foo.git
> repository.
For your information, I have in my drafts a patch which implement a
similar idea. I think I would be able to send a first version in 1 or 2
weeks.
BR,
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
next prev parent reply other threads:[~2015-11-16 8:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 4:39 [Buildroot] [PATCH] support/download: fetch all refs on full git clone Vivien Didelot
2015-11-12 11:02 ` Maxime Hadjinlian
2015-11-12 16:12 ` Vivien Didelot
2015-11-12 16:26 ` Maxime Hadjinlian
2015-11-12 17:07 ` Vivien Didelot
2015-11-13 6:49 ` Arnout Vandecappelle
2015-11-13 15:35 ` Vivien Didelot
2015-11-16 8:43 ` Jérôme Pouiller [this message]
2015-11-13 22:48 ` Yann E. MORIN
2015-11-13 23:04 ` Vivien Didelot
2015-11-19 17:38 ` Vivien Didelot
2015-11-29 17:53 ` 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=14498168.cEIkmZpZ53@sagittea \
--to=jezz@sysmic.org \
--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