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

	Commit message (Collapse)	Author	Age
*	response	Joey Hess	2016-05-17
\|
*	followup	Joey Hess	2016-05-17
\|
*	Merge branch 'master' of ssh://git-annex.branchable.com	Joey Hess	2016-05-17
\|\
* \|	Fix crash when entering/changing view in a subdirectory of a repo that has a ↵	Joey Hess	2016-05-17
\| \| \| \| \| \| \| \|	dotfile in its root.
* \|	use indexEnv	Joey Hess	2016-05-17
\| \|
* \|	Work around git bug in handling of relative path to GIT_INDEX_FILE when in a ↵	Joey Hess	2016-05-17
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	subdirectory of the repository. This affected git annex view. It turns out that some other places that use GIT_INDEX_FILE were already working around the bug. I removed the workaround from Annex.Branch since the new workaround will do.
\| *	(no commit message)	Gus	2016-05-17
\| \|
\| *	(no commit message)	adament@c0981cf9fb3a2c013811bae9af9bada8f0fa0886	2016-05-17
\| \|
\| *	(no commit message)	adament@c0981cf9fb3a2c013811bae9af9bada8f0fa0886	2016-05-17
\| \|
\| *	Added a comment: Restarting	Gus	2016-05-17
\| \|
\| *	Added a comment	openmedi	2016-05-16
\|/
*	comment	Joey Hess	2016-05-16
\|
*	comment	Joey Hess	2016-05-16
\|
*	avoid checking locations in regular repo	Joey Hess	2016-05-16
\| \| \| \| \| \|	In commit 07b1aa343b6d82e8f75de606a5647b0a789f76e0 I accidentially made gitAnnexLocation do more work, checking content locations, when used in a regular repo.
*	adjust: Add --fix adjustment, which is useful when the git directory is in a ↵	Joey Hess	2016-05-16
\| \| \| \|	nonstandard place.
*	add: Adding a v6 pointer file used to annex it; now the pointer file is ↵	Joey Hess	2016-05-16
\| \| \| \| \| \|	added to git as-is. (git add of a pointer file already did the right thing)
*	move keys db closure to AutoMerge	Joey Hess	2016-05-16
\| \| \| \| \|	This makes git-annex sync also do it, which makes sure that the keys db info is fresh when doing a sync --content.
*	reorder associated file db update	Joey Hess	2016-05-16
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	There's a potential race where the smudge filter is run at the same time an object is being downloaded. If the download finished after the inAnnex check, and before the keys db was updated, the associated file would not get updated with the downloaded content. I'm not sure this closes the race; it may only narrow the window. Problem is, the keys database needs to communicate between two different processes. In the case of the assistant, the transferkeys command is the other process, and it closes the db handle after getting the file. So, it should re-open the database and so see the update that the smudge filter has written to it. But, what if the smudge filter takes a while to update the database?
*	Merge branch 'master' of ssh://git-annex.branchable.com	Joey Hess	2016-05-16
\|\
* \|	assistant: Fix race in v6 mode that caused downloaded file content to ↵	Joey Hess	2016-05-16
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	sometimes not replace pointer files. The keys database handle needs to be closed after merging, because the smudge filter, in another process, updates the database. Old cached info can be read for a while from the open database handle; closing it ensures that the info written by the smudge filter is available. This is pretty horribly ad-hoc, and it's especially nasty that the transferrer closes the database every time.
* \|	assistant: Fix bug that caused v6 pointer files to be annexed by the assistant.	Joey Hess	2016-05-16
\| \|
* \|	stage pointer file not annex link	Joey Hess	2016-05-16
\| \|
\| *	Added a comment	CandyAngel	2016-05-16
\| \|
\| *	Added a comment: timings	midfield	2016-05-15
\| \|
\| *	Added a comment	openmedi	2016-05-14
\| \|
\| *	Added a comment	openmedi	2016-05-14
\| \|
\| *	Added a comment: The problem was path length	drunken_sapo	2016-05-14
\| \|
\| *	Added a comment: layout reasoning	aslkdjasd@656d48eb766881455ee14c8cd4adabdd14aad892	2016-05-14
\| \|
\| *	Added a comment: adjusting symlink paths	thowz	2016-05-13
\| \|
\| *	Added a comment	drunken_sapo	2016-05-13
\|/
*	adjust: If the adjusted branch already exists, avoid overwriting it, since ↵	Joey Hess	2016-05-13
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	it might contain changes that have not yet been propigated to the original branch. Could not think of a foolproof way to detect if the old adjusted branch was just behind the current branch. It's possible that the user amended the adjusting commit at the head of the adjusted branch, for example. I decided to bail in this situation, instead of just entering the old branch, so that if git annex adjust succeeds the user is always in a current adjusted branch, not some old and out of date one. What could perhaps be done is enter the old branch and then update it. But that seems too magical; the user may have rebased master or something or may not want to propigate the changes from the old branch. Best to error out.
*	found a bad memory use in git	Joey Hess	2016-05-12
\|
*	Merge branch 'master' of ssh://git-annex.branchable.com	Joey Hess	2016-05-12
\|\
* \|	devblog	Joey Hess	2016-05-12
\| \|
\| *	Added a comment: v6 mode	midfield	2016-05-12
\| \|
\| *	(no commit message)	midfield	2016-05-12
\|/
*	webapp: Avoid confusing display of dead remotes.	Joey Hess	2016-05-12
\|
*	followup	Joey Hess	2016-05-12
\|
*	response	Joey Hess	2016-05-12
\|
*	comment	Joey Hess	2016-05-12
\|
*	open bug from forum post	Joey Hess	2016-05-12
\|
*	response	Joey Hess	2016-05-12
\|
*	response	Joey Hess	2016-05-12
\|
*	response	Joey Hess	2016-05-12
\|
*	Merge branch 'master' of ssh://git-annex.branchable.com	Joey Hess	2016-05-12
\|\
* \|	link to my post "proposal for extending smudge/clean filters with raw file ↵	Joey Hess	2016-05-12
\| \| \| \| \| \| \| \|	access"
\| *	Added a comment	openmedi	2016-05-12
\| \|
\| *	Added a comment	openmedi	2016-05-12
\| \|
\| *	Added a comment	openmedi	2016-05-12
\| \|
\| *	(no commit message)	midfield	2016-05-12
\| \|