This commit is contained in:
Joey Hess 2017-08-18 11:21:34 -04:00
parent 0fce5ac3ad
commit ef8b1d86bf
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 0 additions and 42 deletions

View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="http://svario.it/gioele"
nickname="Gioele"
subject="comment 1"
date="2016-08-24T17:13:04Z"
content="""
As of 2016-08-24 there is not standalone tarball for 6.20160808. The \"current\" tarball points to 6.20160720-g9f0428e.
"""]]

View file

@ -1,11 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2016-09-05T19:38:36Z"
content="""
IIRC the OSX autobuilder was down and ended up being moved to a different
host and so I held off updating the standalone builds for this release.
I don't think it makes sense to update them now, so will just skip updating
them for this release and proceed with the next release.
"""]]

View file

@ -1,12 +0,0 @@
[[!comment format=mdwn
username="https://anarc.at/openid/"
nickname="anarcat"
subject="real happy about optimisations!"
date="2016-10-12T15:38:14Z"
content="""
i am grateful and happy to see work on optimisations for git annex find. on repositories with lots of files, `find` is sometimes disappointingly slow (~25k files)... a 50% improvement is pretty awesome!
thank you for your amazing work!
"""]]

View file

@ -1,11 +0,0 @@
[[!comment format=mdwn
username="http://svario.it/gioele"
nickname="Gioele"
avatar="http://cdn.libravatar.org/avatar/af2f2ba0dafe4650011d20f2168d43cff773aba97f55ae5b252bb873f391c1e2"
subject="The `version` command reports 6.20161231-gc8eeb17da"
date="2017-01-03T11:13:32Z"
content="""
If I run `git-annex version` I get `6.20161231-gc8eeb17da` instead of `6.20170101-something`. Not a big deal, but maybe somebody else may be confused by it.
My `git-annex` binary comes from `git-annex-standalone-amd64.tar.gz` (SHA1 `4a82bb7d0276f387e72f8e09e0d2b1f35edb49bd`).
"""]]