From: Timothy Sample <samplet@ngyro.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: "Kyle Meyer" <kyle@kyleam.com>, "Ludovic Courtès" <ludo@gnu.org>,
guix-sysadmin <guix-sysadmin@gnu.org>,
guix-devel@gnu.org
Subject: Re: Git-LFS or Git Annex?
Date: Sat, 27 Jan 2024 10:59:24 -0600 [thread overview]
Message-ID: <87y1ca90gj.fsf@ngyro.com> (raw)
In-Reply-To: <87ttn0za2m.fsf@gmail.com> (Simon Tournier's message of "Fri, 26 Jan 2024 11:02:41 +0100")
Simon Tournier <zimon.toutoune@gmail.com> writes:
>> Special remotes can also be written in other languages:
>>
>> https://git-annex.branchable.com/design/external_special_remote_protocol/
>
> Thanks! I did not know. Indeed, it could be a nice GSoC to implement
> some ‘git-annex-backend-nar’. :-)
I’ve written a special remote in Guile. If anyone wants to do so, the
following file might help. It implements the basic protocol.
https://git.ngyro.com/git-annex-remote-clouda/tree/git-annex-remote-clouda/remote.scm
More generally, I’m a fan of git-annex. The basic idea is both good and
simple: manage content-addressed, external references in a Git repo. My
biggest complaint is that the interface and its many features often
obscure this simplicity.
-- Tim
next prev parent reply other threads:[~2024-01-27 17:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 15:22 Git-LFS or Git Annex? Ludovic Courtès
2024-01-24 16:13 ` indieterminacy
2024-01-24 17:39 ` Giovanni Biscuolo
2024-01-28 10:33 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2024-01-28 11:32 ` Philip McGrath
2024-01-28 17:32 ` Giovanni Biscuolo
2024-01-29 11:39 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2024-01-24 18:41 ` pukkamustard
2024-01-24 20:32 ` Troy Figiel
2024-01-25 12:03 ` Giovanni Biscuolo
2024-01-25 16:55 ` Simon Tournier
2024-01-26 2:20 ` Kyle Meyer
2024-01-26 10:02 ` Simon Tournier
2024-01-27 16:59 ` Timothy Sample [this message]
2024-01-27 17:47 ` Kyle Meyer
2024-02-14 15:18 ` Simon Tournier
2024-01-27 4:31 ` Philip McGrath
2024-01-28 17:37 ` Efraim Flashner
2024-02-02 16:46 ` Christine Lemmer-Webber
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=87y1ca90gj.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=guix-devel@gnu.org \
--cc=guix-sysadmin@gnu.org \
--cc=kyle@kyleam.com \
--cc=ludo@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).