unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Maxime Devos <maximedevos@telenet.be>, 57858@debbugs.gnu.org
Subject: [bug#57858] [PATCH] gnu: git-annex: Promote git to propagated input
Date: Sat, 17 Sep 2022 11:56:23 +0200	[thread overview]
Message-ID: <m1tu562uk8.fsf@fastmail.net> (raw)
In-Reply-To: <e7f93e43-0caf-de31-aa91-01eb64a2d24c@telenet.be>

Maxime Devos <maximedevos@telenet.be> writes:

> What's the reason for this patch?  My guess is that it's because 
> git-annex cannot find git:

That was indeed the starting point. But...

> If so, propagation (which as a few small downsides) can be avoided with 
> an appropriate substitute* fixing the file name of the git binary.

... I tried that and still got error messages whose exact cause I don't
quite understand.

What made me opt for git as a propagated input is that (1) it works just
fine and (2) there isn't much you can do with git-annex without having
git as well. git is even the official user interface of git-annex.

Cheers,
  Konrad




  reply	other threads:[~2022-09-17  9:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 12:37 [bug#57858] [PATCH] gnu: git-annex: Promote git to propagated input Konrad Hinsen
2022-09-16 15:02 ` Maxime Devos
2022-09-17  9:56   ` Konrad Hinsen [this message]
2022-10-17  8:07     ` bug#57858: " Ludovic Courtès
2022-10-17  9:29       ` [bug#57858] " zimoun
2022-10-17 10:11         ` Konrad Hinsen
2022-10-17 11:02           ` zimoun
2022-10-17 12:55           ` Maxime Devos

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m1tu562uk8.fsf@fastmail.net \
    --to=konrad.hinsen@fastmail.net \
    --cc=57858@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).