-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
git-annex: support forking #36
Comments
The key seems to be
Then copying the annex files was much faster
And the counts come out showing they are indeed now avoiding the duplication:
The git-annex manpage says
which I guess means gitea is not doing It also warns
but I think that's just..a standard assumption we always have to live with (git-annex makes a lot of design choices and assumptions that aren't actually enforceable in like, physical reality, where entropy exists.) Note: this triggered #32, in a different way than before, because the |
tl;dr:
|
I just forked https://data.dev.neuropoly.org/neuropoly/spine-generic-single -> https://data.dev.neuropoly.org/kousu/spine-generic-single.
Server side, this caused a local clone:
and per git-clone(1)
Evidence
And to make doubly sure, here's looking one up by it's actual inode number:
But the repo sizes are wildly different: ~885MB vs ~1.5MB:
And this is of course because it didn't clone the annex files:
and of course this means the repo is broken
same for ssh:
But if I run
git annex get
inside the remote repoThen it works
So, we need to add calling
git annex get
to the Gitea "Fork" button -- but only in git-annex repos, of course.However, if we can, we should try to use hardlinks the way
git clone
does, as thegit annex get
I ran above actually made copiesThe text was updated successfully, but these errors were encountered: