From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH (pushed)] libsanitizer: use git clone --depth 1
Date: Tue, 15 Nov 2022 14:19:04 +0100 [thread overview]
Message-ID: <00f99859-ed54-0e2b-3b62-3272f8477429@suse.cz> (raw)
Using depth == 1 it makes the cloning much faster.
libsanitizer/ChangeLog:
* merge.sh: Use git clone --depth 1.
---
libsanitizer/merge.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libsanitizer/merge.sh b/libsanitizer/merge.sh
index 95ded4f9634..7d1b553e2bb 100755
--- a/libsanitizer/merge.sh
+++ b/libsanitizer/merge.sh
@@ -6,7 +6,7 @@
get_upstream() {
rm -rf upstream
- git clone https://github.com/llvm/llvm-project.git upstream
+ git clone --depth 1 https://github.com/llvm/llvm-project.git upstream
}
get_current_rev() {
--
2.38.1
reply other threads:[~2022-11-15 13:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=00f99859-ed54-0e2b-3b62-3272f8477429@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).