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

	Commit message (Collapse)	Author	Age
*	S3 updates; gpg keys	Joey Hess	2011-03-28
\|
*	will need gpg encryption for s3	Joey Hess	2011-03-28
\|
*	more s3 docs	Joey Hess	2011-03-28
\|
*	document S3 remotes	Joey Hess	2011-03-27
\|
*	bit about bare repos	http://joey.kitenet.net/	2011-03-23
\|
*	Added a comment	http://joey.kitenet.net/	2011-03-23
\|
*	Added a comment	https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U	2011-03-23
\|
*	Added a comment	http://joey.kitenet.net/	2011-03-23
\|
*	Added a comment	https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U	2011-03-22
\|
*	Added a comment	http://joey.kitenet.net/	2011-03-19
\|
*	Added a comment	https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U	2011-03-19
\|
*	remove bad information	Joey Hess	2011-03-18
\| \| \| \| \| \| \| \| \| \| \| \| \|	You do not need to pull from a remote to make git-annex aware of it. Pulling only makes git know about remote/master branches, but git-annex does not care about that. When git-annex encounters a remote in .git/config that has no recorded annex.uuid, it connects to it to get the uuid automatically, and will immediately start using it. A later part of this walkthrough shows how to pull from a remote in order to get its location tracking info, so that git-annex can retrieve files from it. That's the right place to document the need to pull from a remote periodically.
*	(no commit message)	https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U	2011-03-18
\|
*	initial pass at doc update	Joey Hess	2011-03-15
\|
*	update	Joey Hess	2011-03-09
\|
*	be more clear about the rsync usage	http://m-f-k.myopenid.com/	2011-03-06
\|
*	formatting	Joey Hess	2011-03-03
\|
*	document describe command	Joey Hess	2011-03-03
\|
*	split the walkthrough and inline back together	Joey Hess	2011-02-27