cleanup
This commit is contained in:
parent
d1dabb3327
commit
a59148c3a7
5 changed files with 0 additions and 53 deletions
|
@ -1,10 +0,0 @@
|
|||
[[!comment format=mdwn
|
||||
username="zfnupbos@a80a4f4cf5dde7ac4988ef0d077052c95fe1e058"
|
||||
nickname="zfnupbos"
|
||||
subject="version clarification"
|
||||
date="2016-05-04T01:05:52Z"
|
||||
content="""
|
||||
is this 6.20160419 or 6.20160428?
|
||||
|
||||
It was released on the 28th, and 'git-annex version' shows git-annex version: 6.20160428-g1f253e8. But many places refer to it as 6.20160419.
|
||||
"""]]
|
|
@ -1,14 +0,0 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 2"""
|
||||
date="2016-05-04T17:19:17Z"
|
||||
content="""
|
||||
I should have changed the version number to 6.20160428, but I forgot to do
|
||||
so.
|
||||
|
||||
The version shows up in `git annex version` because it uses the build
|
||||
date there, for autobuilds.
|
||||
|
||||
So in short, both versions are equivilant, and both contain the security
|
||||
fix.
|
||||
"""]]
|
|
@ -1,9 +0,0 @@
|
|||
[[!comment format=mdwn
|
||||
username="CandyAngel"
|
||||
subject="comment 1"
|
||||
date="2016-05-16T11:41:08Z"
|
||||
content="""
|
||||
I've very happy to report that the git-add, git-annex-fsck & 'git-annex-reinject --known' workflow is working great!
|
||||
|
||||
Thank you for adding these :)
|
||||
"""]]
|
|
@ -1,9 +0,0 @@
|
|||
[[!comment format=mdwn
|
||||
username="CandyAngel"
|
||||
subject="comment 1"
|
||||
date="2016-06-21T08:46:50Z"
|
||||
content="""
|
||||
Improve SHA*E extension extraction code.
|
||||
|
||||
This sounds really likely to break things like [recovering files by readding](https://git-annex.branchable.com/tips/recover_data_from_lost+found/), because the key is going to be different, despite having the same backend..
|
||||
"""]]
|
|
@ -1,11 +0,0 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 2"""
|
||||
date="2016-07-12T19:55:52Z"
|
||||
content="""
|
||||
In this case, the change only makes eg, "foo.ba__________r" not be considered
|
||||
to have an extension of ".bar". So it's unlikely to affect many files.
|
||||
|
||||
I do try to keep the extension guessing code fairly stable to prevent breaking
|
||||
re-adding. But sometimes a bug does warrant changing it.
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue