From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] support/download/git: Prioritize remote archive
Date: Thu, 18 Aug 2016 19:09:25 +0200 [thread overview]
Message-ID: <20160818170925.GC5930@free.fr> (raw)
In-Reply-To: <1471469135-19009-1-git-send-email-kamath.ben@gmail.com>
Benjamin, All,
On 2016-08-17 14:25 -0700, Benjamin Kamath spake thusly:
> From: Benjamin Kamath <bkamath@spaceflight.com>
>
> Attempt to do a remote archive since it shortcuts us past a few steps when
> available. Additionally. if the git server has uploadArchive.allowUnreachable
> set to true, then this method can also work on arbitrary sha1s, offering a huge
> speed advantage over a full clone.
>
> Signed-off-by: Benjamin Kamath <bkamath@spaceflight.com>
> ---
> Changes v1 -> v2:
> - Skip remote archive for repositories with submodules (suggested by Yann)
>
> support/download/git | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/support/download/git b/support/download/git
> index 416cd1b..d060cbd 100755
> --- a/support/download/git
> +++ b/support/download/git
> @@ -36,6 +36,17 @@ _git() {
> eval ${GIT} "${@}"
> }
>
> +# Try a remote archive, since it is as fast as a shallow clone and can give us
> +# an archive directly. Also, if uploadArchive.allowUnreachable is set to true
> +# on the remote, this will also work for arbitrary sha1s, and will offer a
> +# considerable speedup over a full clone. This will not work for submodules.
> +if [ ${recurse} -eq 0 ]; then
> + printf "Doing remote archive\n"
> + if _git archive --format=tar.gz --prefix=${basename}/ --remote=${repo} -o ${output} ${cset} 2>&1; then
> + exit 0
I would have also done:
else
printf "Remote archive failed, falling back to cloning\n"
Like we do for the shallow clone.
Also, why do you redirect stderr? We don't do it in the clone commands.
We only do it to fetch the special references (gitHub PRs of Gerrit
changes) because it does not make sense to display an spurious message
when the reference is in fact not special.
Regards,
Yann E. MORIN.
> + fi
> +fi
> +
> # Try a shallow clone, since it is faster than a full clone - but that only
> # works if the version is a ref (tag or branch). Before trying to do a shallow
> # clone we check if ${cset} is in the list provided by git ls-remote. If not
> --
> 2.7.4
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-08-18 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 21:25 [Buildroot] [PATCH v2] support/download/git: Prioritize remote archive Benjamin Kamath
2016-08-17 21:53 ` Yann E. MORIN
2016-08-17 22:17 ` Benjamin Kamath
2016-08-18 9:10 ` Yann E. MORIN
2016-08-18 9:26 ` Benjamin Kamath
2016-08-18 9:33 ` Yann E. MORIN
2016-08-18 17:09 ` Yann E. MORIN [this message]
2016-08-24 17:47 ` [Buildroot] [PATCH v3] " Benjamin Kamath
2017-02-12 22:01 ` Arnout Vandecappelle
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=20160818170925.GC5930@free.fr \
--to=yann.morin.1998@free.fr \
--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