| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
to avoid long delay after
|
| | |
|
| | |
|
| |
|
|
| |
Doubles the speed of fsck, and speeds up drop as well.
|
| | |
|
| | |
|
| |
|
|
|
| |
--cached is needed when calling git-diff-index, as it is not diffing
against currently checked out branch.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Only "partially" because the journal is not locked during the merge, so
there's a small window where a different git-annex process could write info
to the journal that overwrites info taken from the merge.
That could be dealt with by locking, but the lock would really need to be
around the whole git-annex, to only let one run at a time. Otherwise, even
with the journal locked during the merge, another git-annex could already
be running, generate an overwriting change, and only store it in the journal
after the merge was complete. And similarly, two git-annex processes could
fight and overwrite each other's information independant of any merging.
So, a toplevel lock for git-annex may get added; it's something I've
considered before, as these potential, unlikely problems are not new.
(OTOH, fsck will deal with such problems.)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Now that branches are more likely, unused needs to more explicitly warn
that it does not look in them.
|
| | |
|
| | |
|
| |
|
|
|
| |
The journal sped this up approximatly 100-fold; it runs in just a few
minutes for a large repository with 30 thousand log files.
|
| |
|
|
|
|
|
|
| |
git is slow when the index file is large and has to be rewritten each time
a file is changed. To speed this up, added a journal where changes are
recorded before being fed into the index file and committed to the
git-annex branch. The entire journal can be fed into git with just 2
commands, and only one write of the index file.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
but write the index file a lot, so slow
|
| | |
|
| |
|
|
|
|
| |
That sucking sound is a whole page of code vanishing to be replaced with
return . catMaybes . map (logFileKey . takeFileName) =<< Branch.files
What can I say, git is my database, and haskell my copilot.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This fixes precommit, since in that hook, git sets the env var to write
to the lock file, which avoids git add failing due to the presence of the
lock file. (Took me a good hour and a half of confusion to figure this out.)
Test suite now passes 100%! Only the upgrade code still remains to be
written.
|
| |
|
|
|
|
|
| |
Otherwise, the location log changes are only staged in its index,
and this can confuse matters if pulling or cloning from the remote.
The test suite was failing because this wasn't done.
|
| | |
|
| |
|
|
|
| |
Use GitRepo functions to call git, the bug occurred when it was run
in a git repo that was not the same as the repo being acted on.
|
| | |
|
| |
|
|
|
| |
This seemed much too hard to do. I just wanted to close stderr
when running it.
|
| | |
|
| | |
|
| |
|
|
|
| |
Many more commands can work in bare repos now, thanks to the git-annex
branch.
|
| |
|
|
|
|
|
|
|
| |
Do not set annex.version whenever any command is run. Just do it in init.
This ensures that, if a repo has annex.version=3, it has a git-annex
branch, so we don't have to run a command every time to check for the
branch.
Remove the old ad-hoc logic for v0 and v1, to simplify version checking.
|
| | |
|
| | |
|
| |
|
|
| |
don't just pull master.. pull everything
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
.. and I think that's everything that will use the branch
|
| | |
|
| | |
|
Joey Hess