From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Konrad Hinsen" <konrad.hinsen@fastmail.net>
Cc: 57858-done@debbugs.gnu.org, Maxime Devos <maximedevos@telenet.be>
Subject: [bug#57858] [PATCH] gnu: git-annex: Promote git to propagated input
Date: Mon, 17 Oct 2022 11:29:52 +0200 [thread overview]
Message-ID: <87lepen6gf.fsf@gmail.com> (raw)
In-Reply-To: <87pmeqhnzh.fsf_-_@gnu.org>
Hi,
On lun., 17 oct. 2022 at 10:07, Ludovic Courtès <ludo@gnu.org> wrote:
>> 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.
>
> Yeah, that sounds reasonable: I’d have made the same suggestion as
> Maxime but any improvement here is welcome.
We are usually not propagating. For example, emacs-magit or git-lfs or
etc.
From my understanding, this change is not coherent with other parts.
About (2), what do you mean Konrad? Is ’git-annex’ not working as
expected? Well, ’git annex’ is a shorthand for ’git-annex’ and I
thought this ’git-annex’ is self-contained; for which operations
’git-annex’ depends on the ’git’ binaires?
Cheers,
simon
next prev parent reply other threads:[~2022-10-17 9:34 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
2022-10-17 8:07 ` bug#57858: " Ludovic Courtès
2022-10-17 9:29 ` zimoun [this message]
2022-10-17 10:11 ` [bug#57858] " 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=87lepen6gf.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=57858-done@debbugs.gnu.org \
--cc=konrad.hinsen@fastmail.net \
--cc=ludo@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).