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 2023-07-15 12:28:32 -04:00
parent d07cc31792
commit 116b8affe5
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 18 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

18
doc/bugs/Changing_sync_to_include_content_breaks_UX/comment_15_38a0eafe91e05a7784dd5e305f38a8f3._comment Normal file
View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="joey"
subject="""comment 15"""
date="2023-07-15T16:09:46Z"
content="""
My current thinking is that when a repository does not have a preferred
content expression, a content sync could avoid adding content to it.
This would avoid surprising behavior after the transition, except for
repositories that did at some time have a preferred content expression set,
but one that no longer reflects the use of the repository.
However, current users of `sync --content` (or of annex.synccontent) do
expect it to fill their repositories that don't have preferred content
configured. So would a sync that defaults to content syncing then need to
behave differently than an explicit `sync --content`? Or should changing
behavior in that case also be part of the transition?
"""]]