From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] support/download: fetch all refs on full git clone
Date: Fri, 6 Nov 2015 23:39:24 -0500 [thread overview]
Message-ID: <1446871164-19229-1-git-send-email-vivien.didelot@savoirfairelinux.com> (raw)
When specifying BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION, a user may want to
specify the SHA of a reference different than a branch or tag.
For instance, Gerrit stores the patchsets under refs/changes/xx/xxx, and
Github stores the pull requests under refs/pull/xxx/head.
When cloning a repository with --bare, you don't fetch these references.
This patch uses --mirror for a full clone, in order to give the user
access to all references of the Git repository.
Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
---
support/download/git | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/support/download/git b/support/download/git
index 0e6103b..357a558 100755
--- a/support/download/git
+++ b/support/download/git
@@ -43,7 +43,7 @@ if [ -n "$(${GIT} ls-remote "${repo}" "${cset}" 2>&1)" ]; then
fi
if [ ${git_done} -eq 0 ]; then
printf "Doing full clone\n"
- ${GIT} clone ${verbose} --bare "${repo}" "${basename}"
+ ${GIT} clone ${verbose} --mirror "${repo}" "${basename}"
fi
GIT_DIR="${basename}" \
--
2.6.2
next reply other threads:[~2015-11-07 4:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 4:39 Vivien Didelot [this message]
2015-11-12 11:02 ` [Buildroot] [PATCH] support/download: fetch all refs on full git clone 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
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=1446871164-19229-1-git-send-email-vivien.didelot@savoirfairelinux.com \
--to=vivien.didelot@savoirfairelinux.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.