Merge branch 'master' of ssh://git-annex.branchable.com
This commit is contained in:
commit
f410f9d7ca
4 changed files with 61 additions and 0 deletions
12
doc/bugs/describe_what_git-annex_actually_is.mdwn
Normal file
12
doc/bugs/describe_what_git-annex_actually_is.mdwn
Normal file
|
@ -0,0 +1,12 @@
|
|||
The homepage lists lots of things, but does not succinctly specify the core of git-annex.
|
||||
It took me multiple sifts through the pages and a failed attempt at setting it up to discover that, and how it does not do what I currently need.
|
||||
|
||||
> git-annex allows managing files with git, without checking the file contents into git.
|
||||
> While that may seem paradoxical, it is useful when dealing with files larger than git can currently easily handle, whether due to limitations in memory, time, or disk space.
|
||||
|
||||
The second sentence does not really help to explain the tool, for me it sounds a lot like git-lfs. My suggestion:
|
||||
|
||||
> git-annex is a sparse file management tool that tracks files separately from their contents.
|
||||
> It enables managing files larger than git can easily handle, whether due to limitations in memory, time, or disk space.
|
||||
|
||||
Still not optimal, but feels a little more precise
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="Lukey"
|
||||
avatar="http://cdn.libravatar.org/avatar/c7c08e2efd29c692cc017c4a4ca3406b"
|
||||
subject="comment 1"
|
||||
date="2021-11-08T19:38:35Z"
|
||||
content="""
|
||||
Describing what `git-annex` does is pretty hard. So when I talk about it, I usually say what you can do with it: manage, sync, backup and archive your data, offline and online, with everything checksummed.
|
||||
"""]]
|
33
doc/bugs/uninit_errors_out_on_repo_without_commits.mdwn
Normal file
33
doc/bugs/uninit_errors_out_on_repo_without_commits.mdwn
Normal file
|
@ -0,0 +1,33 @@
|
|||
### Please describe the problem.
|
||||
```
|
||||
❯ git annex uninit
|
||||
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
|
||||
Use '--' to separate paths from revisions, like this:
|
||||
'git <command> [<revision>...] -- [<file>...]'
|
||||
error: branch 'git-annex' not found.
|
||||
git-annex: git [Param "branch",Param "-D",Param "git-annex"] failed
|
||||
CallStack (from HasCallStack):
|
||||
error, called at ./Git/Command.hs:42:17 in main:Git.Command
|
||||
```
|
||||
|
||||
### What steps will reproduce the problem?
|
||||
|
||||
I guess:
|
||||
- git annex init
|
||||
- git annex uninit
|
||||
But I fear about my files so I won't try
|
||||
|
||||
### What version of git-annex are you using? On what operating system?
|
||||
|
||||
latest on arch linux
|
||||
```sh
|
||||
❯ git annex version
|
||||
git-annex version: 8.20210803-g9cae7c5bb
|
||||
build flags: Assistant Webapp Pairing Inotify DBus DesktopNotify TorrentParser MagicMime Feeds Testsuite S3 WebDAV
|
||||
dependency versions: aws-0.22 bloomfilter-2.0.1.0 cryptonite-0.29 DAV-1.3.4 feed-1.3.2.0 ghc-9.0.1 http-client-0.7.9 persistent-sqlite-2.13.0.3 torrent-10000.1.1 uuid-1.3.15 yesod-1.6.1.2
|
||||
key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 BLAKE2B256E BLAKE2B256 BLAKE2B512E BLAKE2B512 BLAKE2B160E BLAKE2B160 BLAKE2B224E BLAKE2B224 BLAKE2B384E BLAKE2B384 BLAKE2BP512E BLAKE2BP512 BLAKE2S256E BLAKE2S256 BLAKE2S160E BLAKE2S160 BLAKE2S224E BLAKE2S224 BLAKE2SP256E BLAKE2SP256 BLAKE2SP224E BLAKE2SP224 SHA1E SHA1 MD5E MD5 WORM URL X*
|
||||
remote types: git gcrypt p2p S3 bup directory rsync web bittorrent webdav adb tahoe glacier ddar git-lfs httpalso borg hook external
|
||||
operating system: linux x86_64
|
||||
supported repository versions: 8
|
||||
upgrade supported from repository versions: 0 1 2 3 4 5 6 7
|
||||
```
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="Ilya_Shlyakhter"
|
||||
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
|
||||
subject="comment 1"
|
||||
date="2021-11-08T16:34:29Z"
|
||||
content="""
|
||||
These changes would not affect locked-files-only repos, correct?
|
||||
"""]]
|
Loading…
Reference in a new issue