git-annex-gpl - git-annex without the AGPL

	Commit message (Collapse)	Author	Age
*	New annex.synccontent config setting	Joey Hess	2017-02-03
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	.. which can be set to true to make git annex sync default to --content. This may become the default at some point in the future. As well as being configuable by git config, it can be configured by git-annex config to control the default behavior in all clones of a repository. Had to add a separate --no-content switch to we can tell if it's been explicitly set, and should override annex.synccontent. If --content was the default, this complication would not be necessary. This commit was sponsored by Jake Vosloo on Patreon.
*	config: New command for storing configuration in the git-annex branch.	Joey Hess	2017-01-30
\| \| \| \| \| \| \| \| \| \| \|	Any config names can be set using this; git-annex commands will only look at specific ones that make sense and are worth the overhead of querying the branch. This might also be useful for storing whatever other config-type stuff the user might want to shove into the git-annex branch. This commit was sponsored by Jochen Bartl on Patreon.
*	(no commit message)	mark@6b90344cdab3158eacb94a3944460d138afc9bef	2016-01-05
\|
*	sync: Add --no-commit, --no-pull, --no-push options to turn off parts of the ↵	Joey Hess	2015-09-13
\| \| \| \|	sync process, as well as supporting --commit, --pull, --push, and --no-content options to specify the (current) default behavior.
*	sync: Support --jobs	Joey Hess	2015-08-14
\| \| \| \| \| \|	* sync: Support --jobs * sync --content: Avoid unnecessary second pull from remotes when no file transfers are made.
*	on second thought, sync --content --unused is probably not useful, remove	Joey Hess	2015-06-16
\|
*	sync: Add support for --all and --unused.	Joey Hess	2015-06-16
\|
*	doc/*.mdwn: Various typo fixes	Øyvind A. Holm	2015-05-30
\|
*	expand manpages cross-references significantly	Antoine Beaupré	2015-05-29
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	splitting up the man page	Joey Hess	2015-03-23
	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..