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

analysis

Browse source
This commit is contained in:
Joey Hess 2016-12-13 10:40:50 -04:00
parent 6f502c859b
commit d35d87d8d8
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
1 changed files with 16 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

16
doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2016-12-13T14:40:02Z"
content="""
I thought this would involve the journal, but it seems not; same
behavior occurs if the journal is committed after each metadata change.
Looking at the new metadata value in the case where a and c both get set,
it is:
MetaData (fromList [(MetaField "f",fromList [MetaValue (CurrentlySet True) "a",MetaValue (CurrentlySet False) "c"])])
That is supposed to unset c, with the CurrentlySet False, but instead c
remains set somehow.
"""]]