From: Troy Figiel <troy@troyfigiel.com>
To: guix-devel@gnu.org
Subject: Re: Git-LFS or Git Annex?
Date: Wed, 24 Jan 2024 21:32:12 +0100 [thread overview]
Message-ID: <148a15e6-32a5-4a41-8af2-eb136e9b0c8f@troyfigiel.com> (raw)
In-Reply-To: <86jznyy13e.fsf@posteo.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 639 bytes --]
Hi all,
On 2024-01-24 19:41, pukkamustard wrote:
> I've used Git Annex for managing many large files (~100s of GiBs) and it
> worked. However, I found Git Annex to be quite complex and to do things
> automatically without me fully realizing.
>
I can mirror this sentiment. As far as my experience with git-annex
goes, it is a very flexible tool, but difficult to grok.
Although both are FOSS, only git-annex is mostly copyleft with the
(A)GPL3+. git-lfs I believe is copyrighted mainly by two large companies
(GitHub and Atlassian) under a non-copyleft license. Something to keep
in mind at least.
Best wishes,
Troy
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 6367 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-24 20:33 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 [this message]
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
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=148a15e6-32a5-4a41-8af2-eb136e9b0c8f@troyfigiel.com \
--to=troy@troyfigiel.com \
--cc=guix-devel@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 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).