Merge branch 'master' of ssh://git-annex.branchable.com
This commit is contained in:
commit
ba636a803e
6 changed files with 48 additions and 0 deletions
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawkBTVYS5lTecuenAB01eHgfUxE20vWVpU4"
|
||||
nickname="Peng"
|
||||
subject="Large Mountain Loin package size"
|
||||
date="2012-12-28T22:17:43Z"
|
||||
content="""
|
||||
I see that git-annex package file is 489.9MB on Mac Mountain Loin (git-annex.dmg.bz2). The file git-annex.dmg.bz2 is only of size 24M. Is there any way to reduce the package size?
|
||||
"""]]
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA"
|
||||
nickname="Laszlo"
|
||||
subject="comment 1"
|
||||
date="2012-12-28T23:53:22Z"
|
||||
content="""
|
||||
Make a release please, Im eager to try it out!:)
|
||||
"""]]
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawnFhHPFP7j3wGNgBxEJoA8LcBJ4Xd1tTMY"
|
||||
nickname="Joe"
|
||||
subject="Release + Version Number"
|
||||
date="2012-12-29T11:16:05Z"
|
||||
content="""
|
||||
I second Laszlo's request for a release! Also, could you include a version number of some sort on the download (and binary if there isn't one there) to make it easy to tell what is available for download vs. what is installed?
|
||||
"""]]
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
|
||||
nickname="Jimmy"
|
||||
subject="comment 3"
|
||||
date="2012-12-29T13:26:30Z"
|
||||
content="""
|
||||
There are daily/hourly builds at the [[install/OSX]] install page, try out the new features from there
|
||||
"""]]
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://phil.0x539.de/"
|
||||
nickname="Philipp Kern"
|
||||
subject="comment 1"
|
||||
date="2012-12-28T23:23:29Z"
|
||||
content="""
|
||||
Doesn't the encryption part already write an encrypted version completely to disk before starting to upload? (At least with the rsync remote?) So the disk space and I/O usage is already there. (Except that it's probably a temporary file that's deleted after it was created, so that it's not kept around by the filesystem when certain destructive events strike.)
|
||||
"""]]
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog"
|
||||
nickname="Michael"
|
||||
subject="comment 2"
|
||||
date="2012-12-29T08:00:56Z"
|
||||
content="""
|
||||
Being able to resume transfers of encrypted files would absolutely be useful! Disk space is cheap, but bandwidth is not.
|
||||
"""]]
|
Loading…
Add table
Reference in a new issue