close
This commit is contained in:
parent
c2184e2295
commit
511e711bed
2 changed files with 17 additions and 0 deletions
|
@ -98,3 +98,5 @@ git config annex.diskreserve 100M
|
||||||
|
|
||||||
### 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)
|
||||||
|
|
||||||
|
> [[done]] since this has pretty strongly been confirmed to be a bug that
|
||||||
|
> was already fixed in a newer git-annex version. --[[Joey]]
|
||||||
|
|
|
@ -0,0 +1,15 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 7"""
|
||||||
|
date="2022-09-09T18:50:43Z"
|
||||||
|
content="""
|
||||||
|
Well, it seems that you have confirmed that the bug you were seeing is the
|
||||||
|
known and already fixed problem involving files that had the same size and
|
||||||
|
mtime.
|
||||||
|
|
||||||
|
I suggest filing a new bug report for the other problem, since it does not
|
||||||
|
seem like the same problem. I don't like to have to re-read long threads
|
||||||
|
about unrelated problems to tease out the "current" problem than a bug
|
||||||
|
report is talking about. 1 bug report per problem saves everyone time and
|
||||||
|
confusion.
|
||||||
|
"""]]
|
Loading…
Reference in a new issue