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

comment

Browse source
This commit is contained in:
Joey Hess 2022-03-29 14:53:07 -04:00
parent b7c2a8a443
commit bc6d64ec8a
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 54 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

37
doc/todo/force_star_topology_on_a_repository/comment_4_a722bce9ea8c94864657415395eadb43._comment Normal file
View file

@ -0,0 +1,37 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2022-03-29T18:06:51Z"
content="""
`git-annex initremote --private` is the equivilant of annex.private for a
special remote, and sets remote.name.annex-private.
And remote.name.annex-private can also be set to avoid recording anything
about a git-annex remote.
Setting annex.private with `git config` does not affect the remotes.
Which for many use cases of annex.private, is a good thing.
`git-annex config` settings should have the same effect as if the
corresponding `git config` were set. So `git-annex config` of annex.private
is not quite the right thing, since that would not set
remote.name.annex-private.
So, I think you were somewhat on the right track, that there needs to be a
list of uuids of repositories that are not private. And then all other
repositories would behave the same as if annex.private were set for them,
when git-annex is running on them or using them as a remote.
Concretely, this could look like `git-annex config --set annex.privateexcept "uuid1 uuid2"`
Implementation would just involve the two places that currently
check annexPrivateRepos also checking that.
One small problem with this idea is, if you want to add a new non-private
repository or special remote after setting that git-annex config, you would
need to run `git-annex config` to add it to the list first. Otherwise,
information about it won't get recorded publically when it's initialized.
So you would need to generate a uuid by hand, then update the list, then
run `git-annex reinit` with that uuid, or `git-annex initremote` with the
`uuid=` parameter.
"""]]

17
doc/todo/force_star_topology_on_a_repository/comment_5_60d832d97923d3aac047dd525dc8df12._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="joey"
subject="""comment 5"""
date="2022-03-29T18:43:11Z"
content="""
What happens if someone sets this git-annex config, but the repo is also
used by someone else, who does not want to honor that, and wants to have
their own group of git-annex repos that work together as usual?
This is a reasonable difference of opinion to have, and this kind of
disagreement needs to be considered when adding a `git-annex config`
setting.
Usually, `git-annex config` settings can be overridden by
`git config`. So there would need to be a annex.privateexcept
git config as well.
"""]]