From: Greg Hogan <code@greghogan.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 73993@debbugs.gnu.org
Subject: [bug#73993] [PATCH v2 1/3] gnu: git-sizer: Propagate git.
Date: Thu, 26 Dec 2024 14:35:37 -0500 [thread overview]
Message-ID: <CA+3U0Zk0KcPeg6Prwfeb-eKWov_L-Sqa+CcPccDh=JbUDMFMtQ@mail.gmail.com> (raw)
In-Reply-To: <87a5ctmeyl.fsf@gnu.org>
On Wed, Dec 18, 2024 at 6:02 AM Ludovic Courtès <ludo@gnu.org> wrote:
>
> Greg Hogan <code@greghogan.com> skribis:
>
> > Fix the current version of this package, which depends on git from PATH.
> >
> > * gnu/packages/version-control.scm (git-sizer)
> > [native-inputs]: Move git ...
> > [propagated-inputs]: ... to here.
> >
> > Change-Id: Iea70a16845e93f5c3740da5596e61cc2d7fd17b9
>
> [...]
>
> > (propagated-inputs
> > - (list go-github-com-cli-safeexec
> > + (list git
>
> Instead of propagating, it would be nice to record the absolute file
> name in the source.
Ludo',
Thanks for reviewing this. There was already a v3 which consolidated
the patches (I had separated the bugfix from the patch) and is greatly
simplified per Liliana's recommendations.
Greg
next prev parent reply other threads:[~2024-12-26 19:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 19:05 [bug#73993] [PATCH] gnu: git-sizer: Pin git version Greg Hogan
2024-11-29 9:40 ` Liliana Marie Prikler
2024-12-05 21:06 ` Greg Hogan
2024-12-05 21:04 ` [bug#73993] [PATCH v2 0/3] Pin git for git-sizer Greg Hogan
2024-12-05 21:04 ` [bug#73993] [PATCH v2 1/3] gnu: git-sizer: Propagate git Greg Hogan
2024-12-18 11:02 ` Ludovic Courtès
2024-12-26 19:35 ` Greg Hogan [this message]
2024-12-05 21:04 ` [bug#73993] [PATCH v2 2/3] gnu: git-sizer: Use gexps Greg Hogan
2024-12-18 11:03 ` Ludovic Courtès
2024-12-05 21:04 ` [bug#73993] [PATCH v2 3/3] gnu: git-sizer: Pin git version Greg Hogan
2024-12-06 21:19 ` Liliana Marie Prikler
2024-12-09 15:30 ` [bug#73993] [PATCH v3] " Greg Hogan
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+3U0Zk0KcPeg6Prwfeb-eKWov_L-Sqa+CcPccDh=JbUDMFMtQ@mail.gmail.com' \
--to=code@greghogan.com \
--cc=73993@debbugs.gnu.org \
--cc=ludo@gnu.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.