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

close wontfix

Browse source
This commit is contained in:
Joey Hess 2020-02-17 12:53:27 -04:00
parent f4bf2ccc7a
commit 39864fe1b4
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 18 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/annex.genmetadata_should_default_to_true.mdwn
View file

@ -9,3 +9,5 @@ Add a file to a fresh annex, observe it has no metadata.
### 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)
Yes I love it! (Except for its spotty timestamp support) Yes I love it! (Except for its spotty timestamp support)
> [[notabug|done]] --[[Joey]]

16
doc/bugs/annex.genmetadata_should_default_to_true/comment_5_8cd47851ca76005e0011da7c2f62d77d._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="joey"
subject="""comment 5"""
date="2020-02-17T16:47:33Z"
content="""
I agree with Ilya's points.
And it's unresonable to characterize this as data loss, because git itself
does not store file timestamp data. Making such mischaracterizations does,
however, cause me, as the maintainer, to wonder if this is a feature that
is worth keeping, since I have no interest in descending that rabbit hole
or fighting such accusations. Generally, going to the strongest possible
argument, when requesting a change, is not actually your best move.
Closing this bug report.
"""]]