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

removed

Browse source
This commit is contained in:
fireboy 2021-11-09 04:47:41 +00:00 committed by admin
parent 6682b04a27
commit 95c37fb262
1 changed files with 0 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
doc/forum/Why_does_adjust_need_a_filepointer_at_all__63__.mdwn
View file

@ -1,12 +0,0 @@
I'm trying to understand why `git annex adjust` changes any symlinks to pointers. All the "pointer file" contains is the git annex object path with the hash, which the symlink also contains. Is there a reason we can't leave the branch untouched and just change the local configuration to track which files are to be adjusted as locked/unlocked? I imagine with this model, we don't even need an adjust command, and we could simply upgrade the old `lock` and `unlock` commands.
```
git annex unlock file1 ## Adds file1 to list of files to run the "adjust" smudge/clean filter for. This data could be stored somewhere in .git/annex, but is completely local and does not need to be synced or protected anywhere.
git annex lock file1 ## Removes file1 from list of files to run the adjust on.
```
What is the advantage?
For one, we don't have extra branches that are potentially confusing. It also simplifies the user facing surface area which is great to reduce user-causing-bugs.
Thoughts?