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

comment and close, not a bug really

Browse source
This commit is contained in:
Joey Hess 2022-02-21 15:39:38 -04:00
parent 80f244d7b6
commit ba907b6682
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 21 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/make___39__find__39___clear__40__er__41___on_what_is_unlocked_.mdwn
View file

@ -61,3 +61,5 @@ no changes added to commit (use "git add" and/or "git commit -a")
```
and I do not think it should report `124` as unlocked. Or is there some `find` way to search only for "truly unlocked" files?
> [[notabug|done]] --[[Joey]]

19
doc/bugs/make___39__find__39___clear__40__er__41___on_what_is_unlocked_/comment_1_b855c810464bb22bd76681d669313ae5._comment Normal file
View file

@ -0,0 +1,19 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2022-02-21T19:16:13Z"
content="""
The only difference between those two is that git-annex unlock stages the
unlocking, while replacing the file with unlocked content does not stage
it yet.
Both files are unlocked in the working tree though. One is unlocked in
the index, and the other one is not yet. But git-annex find examines the
working tree.
What you are looking for is a a way to have `git-annex find`
ignore the working tree and find files that are unlocked in the index.
That is doable:
git-annex find --branch=$(git write-tree) --unlocked
"""]]