Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] suport/download: fix git wrapper with submodules on older git versions
Date: Fri, 29 May 2020 23:41:49 +0200	[thread overview]
Message-ID: <20200529234149.7437a5b4@windsurf.home> (raw)
In-Reply-To: <20200524114718.21707-1-yann.morin.1998@free.fr>

On Sun, 24 May 2020 13:47:18 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> +    # Older versions of git will store the absolute path of the git tree
> +    # in the .git of submodules, while newer versions just use relative
> +    # paths. Detect and fix the older variants to use relative paths, so
> +    # that the archives are reproducible across a wider range of git
> +    # versions. However, we can't do that if git is too old and uses
> +    # full repositories for submodules.

If I understand correctly, there are three "eras":

 - Really old Git versions, where full repositories are used for
   submodules, where we can't do anything.

 - Old Git versions, that stored absolute paths.

 - Recent Git versions, that store relative paths.

Would it be possible to identify which versions we're talking about
here? I'm sure you've done that research, and I think it makes sense to
capture that, as we will certainly wonder what we mean by "older
versions", "old version", "new version.

What is new, old, or older today, will feel quite different 5 years
from now.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2020-05-29 21:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-24 11:47 [Buildroot] [PATCH] suport/download: fix git wrapper with submodules on older git versions Yann E. MORIN
2020-05-25  1:55 ` Vincent Fazio
2020-05-25 20:05   ` Yann E. MORIN
2020-05-25 23:24     ` Vincent Fazio
2020-05-29 21:41 ` Thomas Petazzoni [this message]
2020-05-30 21:08   ` 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=20200529234149.7437a5b4@windsurf.home \
    --to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox