| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
Note that the implementation uses replaceFile, so that the actual
replacement of the work tree file is atomic. This seems a good property to
have!
It would be possible for unlock in v6 mode to be run on files that do not
have their content present. However, that would be a behavior change from
before, and I don't see any immediate need to support it, so I didn't
implement it.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
i found that most man pages only had references to the main git-annex
manpage, which i stillfind pretty huge and hard to navigate through.
i tried to sift through all the man pages and add cross-references
between relevant pages. my general rule of thumb is that links should
be both ways unless one of the pages is a more general page that would
become ridiculously huge if all backlinks would be added
(git-annex-preferred-content comes to mind).
i have also make the links one per line as this is how it was done in
the metadata pages so far.
i did everything but the plumbing, utility and test commands, although
some of those are linked from the other commands so cross-links were
added there as well.
|
| |
|
|
|
|
|
|
|
|
| |
One of my
for f in `ls *.mdwn | sort -R`; do aspell -c $f; sleep 2; done
sessions.
3647f704-e510-11e4-bf50-000df06acc56
|
|
|
Common command man pages all split out and often expanded.
A few sections split out into their own pages.
Still need to do all the other commands..
|
Joey Hess
Antoine Beaupré
Øyvind A. Holm