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

comment and moreinfo needed

Browse source
This commit is contained in:
Joey Hess 2020-11-24 15:00:06 -04:00
parent 49584ead91
commit a80bf89e8d
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 29 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/Beware__58___there_is_a_file-losing_bug_in_unused_cmd.mdwn
View file

@ -13,3 +13,5 @@ I'm not sure. The files lost appear to be more recently added files, so this bug
### 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) ### 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)
I've used git-annex to maintain large file sets for years now and there is no better tool I know of. I've used git-annex to maintain large file sets for years now and there is no better tool I know of.
[[!tag moreinfo]]

27
doc/bugs/Beware__58___there_is_a_file-losing_bug_in_unused_cmd/comment_2_dcce85bbbe95a5cee1e6f95a3ab110de._comment Normal file
View file

@ -0,0 +1,27 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2020-11-24T18:37:58Z"
content="""
> The annexes were fully synced and git-annex list showed the files in the annex they were dropped from.
That statement does not make a lot of sense. If both repos have been
synced with the other, then git-annex list could only display the file
if it was still in the master branch. But then git-annex unused would
certianly not have considered it unused. (Unless it has an insanely bad bug,
but the test suite tests that it doesn't have that bug, so it seems likely
it does not.)
But also, if both repos were synced with one-another, and you had dropped the
file from one repo, then git-annex list in other other repo would know that and
would not show the file as still being in it.
Which suggests you mean something else by "fully synced" than being fully in
sync at that point. Or that you were mistaken about them being fully in sync.
And if you were mistaken about that, it's easy to set up situations where
two repos are not fully in sync, and so in one, the file is to all appearances
unused, but in the other one, the file is still in use by a branch.
So, without a way to reproduce this, I have to assume it's user error.
"""]]