From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14396] GIthub schema is broken
Date: Sun, 28 Nov 2021 08:39:15 +0000 [thread overview]
Message-ID: <bug-14396-163-k4CiBJsWWT@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14396-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14396
--- Comment #6 from Jens Maus <mail@jens-maus.de> ---
(In reply to Yann E. MORIN from comment #3)
> Second, this will trigger much bigger downloads, which can be a bit overwhelming
> for large repositories. That latter issue is smoothened by the use of the local
> git cache, so this is only really a problem on the first download.
Please keep in mind that there are a lot of CI driven build environments out
there (like in my case) where no git cache environment is available, thus
packages are always freshly downloaded. Therefore the direct archive download -
rather than doing a full fledged git clone on each run - resulted in
significantly smaller (i.e faster) downloads and thus faster CI build-times.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-11-28 8:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 15:13 [Buildroot] [Bug 14396] New: GIthub schema is broken bugzilla
2021-11-27 12:03 ` [Buildroot] [Bug 14396] " bugzilla
2021-11-27 20:28 ` bugzilla
2021-11-27 21:12 ` bugzilla
2021-11-27 21:32 ` bugzilla
2021-11-27 21:54 ` bugzilla
2021-11-27 22:14 ` bugzilla
2021-11-28 8:39 ` bugzilla [this message]
2021-11-28 15:52 ` bugzilla
2021-11-28 16:28 ` bugzilla
2021-11-28 16:49 ` bugzilla
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=bug-14396-163-k4CiBJsWWT@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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 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.