From: Greg Hogan <code@greghogan.com>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: 70656@debbugs.gnu.org, Tanguy Le Carrour <tanguy@bioneland.org>,
Munyoki Kilyungi <me@bonfacemunyoki.com>,
Christopher Baines <mail@cbaines.net>, jgart <jgart@dismail.de>,
Marius Bakke <marius@gnu.org>,
Sharlatan Hellseher <sharlatanus@gmail.com>
Subject: [bug#70656] [PATCH python-team 3/4] gnu: python-pbr: Use git-minimal/pinned.
Date: Thu, 24 Oct 2024 12:26:02 -0400 [thread overview]
Message-ID: <CA+3U0Zngtj4ENh_eV8cBe1G3KHJWBTHmtCox2R2v6OPVrqGW6A@mail.gmail.com> (raw)
In-Reply-To: <ZjXt9fEFOjnlRgBP@noor.fritz.box>
On Sat, May 4, 2024 at 4:14 AM Lars-Dominik Braun <lars@6xq.net> wrote:
>
> Hi,
>
> > This helps reduce the dependencies on git, as I think it's find to build with
> > a slightly older git, at least during periods when git-minimal/pinned needs
> > updating.
>
> this one is used on the repository cloned during build. As far as I see
> we use git-minimal for cloning. Do we know whether the on-disk structures
> of git are stable, i.e. can a clone of git version A be read by a git
> version B with B < A?
Why do we use git-minimal for cloning instead of git-minimal/pinned?
next prev parent reply other threads:[~2024-10-24 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 20:38 [bug#70656] [PATCH python-team 0/4] Use git-minimal/pinned for some Python packages Christopher Baines
2024-04-29 20:40 ` [bug#70656] [PATCH python-team 1/4] gnu: python-gitpython: Use git-minimal/pinned Christopher Baines
2024-04-29 20:40 ` [bug#70656] [PATCH python-team 2/4] gnu: python-gitdb: " Christopher Baines
2024-04-29 20:40 ` [bug#70656] [PATCH python-team 3/4] gnu: python-pbr: " Christopher Baines
2024-05-04 8:12 ` Lars-Dominik Braun
2024-10-24 16:26 ` Greg Hogan [this message]
2024-04-29 20:40 ` [bug#70656] [PATCH python-team 4/4] gnu: python-versioneer: " Christopher Baines
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=CA+3U0Zngtj4ENh_eV8cBe1G3KHJWBTHmtCox2R2v6OPVrqGW6A@mail.gmail.com \
--to=code@greghogan.com \
--cc=70656@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=mail@cbaines.net \
--cc=marius@gnu.org \
--cc=me@bonfacemunyoki.com \
--cc=sharlatanus@gmail.com \
--cc=tanguy@bioneland.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.