On Thu, Oct 27, 2011 at 19:04, Joey Hess <j...@kitenet.net> wrote:

>> Sounds good. Would that cover the other noted limitations, as well?
>
> Unsure what you mean.

* I can not run git annex fsck (this might be addressed by Joey in code)
* Also, bare git annex repos only know about themselves and not other
repos. Again, this is somewhat expected, but still.


> It's still not safe. Consider A and B are symlinked and B is untrusted.
> Now you run git annex drop in B. It checks that A has a copy of a file..
> good, it does. So it deletes a file... from both.

Agreed. I implicitly assumed that I would never ever drop anything
from either repo.


> Oh, I thought you meant only storing the bup data in a separate branch
> in the same repository. You can have a bup special remote and store your
> data there but it then has to be accessed as a special remote, not as a
> regular bare remote.

The problem is that, afaik, I can't have it as a bare special remote.

The use case is that I built & hosted a server for backups and backups
only. As origin, it's used to sync git state between all other repos
and always keeps a copy of all files, forever. Obviously, I'd like to
keep the bup repo in there, as well.



Thanks,
Richard
_______________________________________________
vcs-home mailing list
vcs-home@lists.madduck.net
http://lists.madduck.net/listinfo/vcs-home

Reply via email to