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

	Commit message (Collapse)	Author	Age
...
\| *	startedTime needs to be a Maybe to handle transfers that have not started yet	Joey Hess	2012-07-02
\| \| \| \| \| \| \| \|	This changes the file format.
* \|	startedTime needs to be a Maybe to handle transfers that have not started yet	Joey Hess	2012-07-02
\|/ \| \| \|	This changes the file format.
*	update	Joey Hess	2012-07-02
\|
*	fix reading of empty filename from transfer info file	Joey Hess	2012-07-02
\|
*	cleanup	Joey Hess	2012-07-02
\|
*	record transfers for git-annex-shell	Joey Hess	2012-07-02
\| \| \| \| \| \| \| \| \|	Not yet tested and places git-annex-shell is run need to be modified to pass the new field settings. Note that rsyncServerSend was changed to fork, rather than directly exec rsync, because it needs to keep the transfer lock held, and clean up the transfer log when done.
*	record transfer information on local git remotes	Joey Hess	2012-07-01
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	In order to record a semi-useful filename associated with the key, this required plumbing the filename all the way through to the remotes' storeKey and retrieveKeyFile. Note that there is potential for deadlock here, narrowly avoided. Suppose the repos are A and B. A sends file foo to B, and at the same time, B gets file foo from A. So, A locks its upload transfer info file, and then locks B's download transfer info file. At the same time, B is taking the two locks in the opposite order. This is only not a deadlock because the lock code does not wait, and aborts. So one of A or B's transfers will be aborted and the other transfer will continue. Whew!
*	bugfixes	Joey Hess	2012-07-01
\| \| \| \| \| \|	fdToHandle seems to close the fd avoid excess trailing newline
*	tested; bugfixes	Joey Hess	2012-07-01
\|
*	add transfer information files	Joey Hess	2012-07-01