rewrote and expanded package description
This commit is contained in:
parent
c151a520c1
commit
e6a432bb56
2 changed files with 24 additions and 14 deletions
19
debian/control
vendored
19
debian/control
vendored
|
@ -108,10 +108,15 @@ Description: manage files with git, without checking their contents into git
|
||||||
dealing with files larger than git can currently easily handle, whether due
|
dealing with files larger than git can currently easily handle, whether due
|
||||||
to limitations in memory, time, or disk space.
|
to limitations in memory, time, or disk space.
|
||||||
.
|
.
|
||||||
Even without file content tracking, being able to manage files with git,
|
It can store large files in many places, from local hard drives, to a
|
||||||
move files around and delete files with versioned directory trees, and use
|
large number of cloud storage services, including S3, WebDAV,
|
||||||
branches and distributed clones, are all very handy reasons to use git. And
|
and rsync, with a dozen cloud storage providers usable via plugins.
|
||||||
annexed files can co-exist in the same git repository with regularly
|
Files can be stored encrypted with gpg, so that the cloud storage
|
||||||
versioned files, which is convenient for maintaining documents, Makefiles,
|
provider cannot see your data. git-annex keeps track of where each file
|
||||||
etc that are associated with annexed files but that benefit from full
|
is stored, so it knows how many copies are available, and has many
|
||||||
revision control.
|
facilities to ensure your data is preserved.
|
||||||
|
.
|
||||||
|
git-annex can also be used to keep a folder in sync between computers,
|
||||||
|
noticing when files are changed, and automatically committing them
|
||||||
|
to git and transferring them to other computers. The git-annex webapp
|
||||||
|
makes it easy to set up and use git-annex this way.
|
||||||
|
|
|
@ -18,13 +18,18 @@ Description:
|
||||||
dealing with files larger than git can currently easily handle, whether due
|
dealing with files larger than git can currently easily handle, whether due
|
||||||
to limitations in memory, time, or disk space.
|
to limitations in memory, time, or disk space.
|
||||||
.
|
.
|
||||||
Even without file content tracking, being able to manage files with git,
|
It can store large files in many places, from local hard drives, to a
|
||||||
move files around and delete files with versioned directory trees, and use
|
large number of cloud storage services, including S3, WebDAV,
|
||||||
branches and distributed clones, are all very handy reasons to use git. And
|
and rsync, with a dozen cloud storage providers usable via plugins.
|
||||||
annexed files can co-exist in the same git repository with regularly
|
Files can be stored encrypted with gpg, so that the cloud storage
|
||||||
versioned files, which is convenient for maintaining documents, Makefiles,
|
provider cannot see your data. git-annex keeps track of where each file
|
||||||
etc that are associated with annexed files but that benefit from full
|
is stored, so it knows how many copies are available, and has many
|
||||||
revision control.
|
facilities to ensure your data is preserved.
|
||||||
|
.
|
||||||
|
git-annex can also be used to keep a folder in sync between computers,
|
||||||
|
noticing when files are changed, and automatically committing them
|
||||||
|
to git and transferring them to other computers. The git-annex webapp
|
||||||
|
makes it easy to set up and use git-annex this way.
|
||||||
|
|
||||||
Flag S3
|
Flag S3
|
||||||
Description: Enable S3 support
|
Description: Enable S3 support
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue