From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] support/download/git: Prioritize remote archive
Date: Thu, 18 Aug 2016 00:00:56 +0200 [thread overview]
Message-ID: <20160817220056.GK5778@free.fr> (raw)
In-Reply-To: <20160817235400.43af6dec@free-electrons.com>
On 2016-08-17 23:54 +0200, Thomas Petazzoni spake thusly:
> Hello,
>
> On Wed, 17 Aug 2016 23:31:02 +0200, Yann E. MORIN wrote:
>
> > So, I think it is safe to assume that git-archives always generates
> > reproducible archive.
>
> So the only remaining reason to not use git archive all the time is to
> support submodules?
Yes.
When doing submodules, I pondered doing two code paths: one for
non-submodules, that would use git-archive, and one where we would do it
all manually as we do today.
But then I concluded that it was better to have a single code path.
Note that, before submodules, we were happily using git-archive locally,
not even forcing the collating rules.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| 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-17 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 19:10 [Buildroot] [PATCH 1/1] support/download/git: Prioritize remote archive Benjamin Kamath
2016-08-17 20:39 ` Thomas Petazzoni
2016-08-17 21:06 ` Benjamin Kamath
2016-08-17 21:03 ` Yann E. MORIN
2016-08-17 21:13 ` Benjamin Kamath
2016-08-17 21:31 ` Yann E. MORIN
2016-08-17 21:54 ` Thomas Petazzoni
2016-08-17 22:00 ` Yann E. MORIN [this message]
2016-08-22 19:53 ` Peter Korsgaard
2016-08-22 20:55 ` Yann E. MORIN
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=20160817220056.GK5778@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