mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

commeent

Browse source
This commit is contained in:
Joey Hess 2022-01-19 11:56:00 -04:00
parent fb11ffe594
commit 2cb7914699
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 19 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
doc/tips/using_nested_git_repositories/comment_2_63f30b652c0cbdb0acf6745891f9f09e._comment Normal file
View file

@ -0,0 +1,19 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2022-01-19T15:51:17Z"
content="""
I agree, submodules are the usual way to nest git repositories, and will
more or less just work with git-annex.
I think that the author of this tip is wanting to version control the
contents of `.git` itself. Eg, to version control `.git/config` and
`.git/hooks/`.
One problem with this approach is that when the outer repository has
"dotgit/annex/objects/` files added to it, running `git-annex drop` inside
the nested git repository will drop the content, but the outer repository
will still contain a copy too. You would have to use `git-annex unused`
to eventually clean up those copies. And it stores 2 copies of every
annexed file to use it this way.
"""]]