From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/1] package/trace-cmd: bump to version 2.9.1
Date: Mon, 4 Jan 2021 18:21:56 +0100 [thread overview]
Message-ID: <20210104172156.GA1485369@scaer> (raw)
In-Reply-To: <CADYdroNCoM6CqOd+bEwLyFbZrmxzUS+r_B+pHkvQDiOYcdtTvw@mail.gmail.com>
Norbert, All,
On 2021-01-04 14:19 +0100, Norbert Lange spake thusly:
> Yann E. MORIN < [1]yann.morin.1998@free.fr> schrieb am So., 3. J?n. 2021, 12:09:
> - keep using a git clone
> Why is a git checkout necessary/preferable ?
s,necessary/,,
1. It was already a git clone previously
2. git clones are cached locally (so re=usable between builds if pne had
exported BR2_DL_DIR ), and git clones are named after the package in
Buildroot, not after the upstream repo (but in this case, the basename
did not change)
3. That tree is not very big (8.18MiB fetched, for a tarball that is
4.1MiB)
4. Except for the first build, fetching new objects is going to be fast
when people update (probably faster than fetching the full archive).
I also have a tendency to prefer git clones, as the archivers on remote
sites have been known to change from time to time. For example, github
has changed the way they create their archives at least twice in the
past few years, which had an impact on our hashes...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2021-01-04 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 10:48 [Buildroot] [PATCH v4 1/1] package/trace-cmd: bump to version 2.9.1 Norbert Lange
2021-01-03 11:09 ` Yann E. MORIN
2021-01-04 13:19 ` Norbert Lange
2021-01-04 17:21 ` Yann E. MORIN [this message]
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=20210104172156.GA1485369@scaer \
--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 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.