close bug report, open todo item
This commit is contained in:
parent
e2c894d3df
commit
361740a112
4 changed files with 26 additions and 1 deletions
|
@ -77,3 +77,5 @@ file_%subdir%
|
|||
|
||||
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
|
||||
Yep! I already use it to move files between my laptop's HDD and SSD, and to copy files between my many SD cards. I was trying this to see if I could not have to scroll as far on my 3D printer's menu.
|
||||
|
||||
> [[done]] see comments --[[Joey]]
|
||||
|
|
|
@ -0,0 +1,17 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 4"""
|
||||
date="2018-10-26T16:53:47Z"
|
||||
content="""
|
||||
`git annex adjust --hide-missing` is now available to do what you want
|
||||
re hiding missing files.
|
||||
|
||||
`git annex view` doesn't currently unlock files in a v6 repo, so it's not
|
||||
usable on a crippled filesystem. That's why the cat in the transcript above
|
||||
shows the symlink content which git writes to a regular file when in a
|
||||
crippled filesystem.
|
||||
|
||||
I would like to eventually unify adjust with view, so `git annex adjust
|
||||
--unlock` can be used with a view, which would support that.
|
||||
See [[todo/unify_adjust_with_view]].
|
||||
"""]]
|
|
@ -8,7 +8,6 @@ git-annex should use smudge/clean filters. v7 mode
|
|||
|
||||
- <http://git-annex.branchable.com/bugs/assistant_crashes_in_TransferScanner/>
|
||||
- <http://git-annex.branchable.com/bugs/v6_appears_to_not_thin/>
|
||||
- <http://git-annex.branchable.com/bugs/Metadata_views_in_v6_repo_upgraded_from_direct_mode_act_strangely/>
|
||||
- <http://git-annex.branchable.com/bugs/git-annex-sync_sometimes_fails_in_submodule_in_V6_adjusted_branch/>
|
||||
|
||||
### long term todos
|
||||
|
|
7
doc/todo/unify_adjust_with_view.mdwn
Normal file
7
doc/todo/unify_adjust_with_view.mdwn
Normal file
|
@ -0,0 +1,7 @@
|
|||
`git annex adjust` and `git annex view` (et all) both derive a branch from
|
||||
the main branch and enter it. They have different capabilies. It would be
|
||||
useful to be able to compose them. For example, to enter a view based on
|
||||
metadata that also has all files unlocked.
|
||||
|
||||
There's also probably a fair amount of overlap in their implementations.
|
||||
--[[Joey]]
|
Loading…
Reference in a new issue