summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* releasing version 3.201111223.20111122Gravatar Joey Hess2011-11-22
|
* find: Support --print0Gravatar Joey Hess2011-11-22
| | | | | | | | | | | It would be nice if command-specific options were supported. The first difficulty is that which command is being called is not known until after getopt; but that could be worked around by finding the first non-dashed parameter. Storing the settings without putting them in the annex monad is the next difficulty; it could perhaps be handled by making the seek stage pass applicable settings into the start stage (and from there on to perform as needed). But that still leaves a problem, what data type to use to represent the options between getopt and seek?
* response; cannot reproduceGravatar Joey Hess2011-11-22
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2011-11-22
|\
| * (no commit message)Gravatar https://www.google.com/accounts/o8/id?id=AItOawnBJ6Dv1glxzzi4qIzGFNa6F-mfHIvv9Ck2011-11-22
| |
* | Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2011-11-21
|\|
| * (no commit message)Gravatar http://cgray.myopenid.com/2011-11-21
| |
* | comment updateGravatar Joey Hess2011-11-20
|/
* responseGravatar Joey Hess2011-11-20
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2011-11-20
|\
* | status --json now shows most thingsGravatar Joey Hess2011-11-20
| | | | | | | | | | | | Left out the backend usage graph for now, and bad/temp directory sizes are only displayed when present. Also, disk usage is returned as a string with units, which I can see changing later.
* | tweaksGravatar Joey Hess2011-11-19
| |
* | tweakGravatar Joey Hess2011-11-19
| |
* | tweakGravatar Joey Hess2011-11-19
| |
* | update comment to explain non-obvious temp fileGravatar Joey Hess2011-11-19
| |
* | avoid error message when doing get --from on file not present on remoteGravatar Joey Hess2011-11-18
| |
| * (no commit message)Gravatar https://www.google.com/accounts/o8/id?id=AItOawnBJ6Dv1glxzzi4qIzGFNa6F-mfHIvv9Ck2011-11-18
|/
* status: Include all special remotes in the list of repositories.Gravatar Joey Hess2011-11-18
| | | | | Special remotes do not always have a description listed in uuid.log, and such ones were not listed before.
* Avoid excessive escaping for rsync special remotes that are not accessed ↵Gravatar Joey Hess2011-11-18
| | | | | | | | | over ssh. This is actually tricky, 45bbf210a1210172c7c7b87879ed74f7c8ccbdba added the escaping because it's needed for rsync that does go over ssh. So I had to detect whether the remote's rsync url will use ssh or not, and vary the escaping.
* responseGravatar Joey Hess2011-11-18
|
* (no commit message)Gravatar http://ertai.myopenid.com/2011-11-18
|
* migrate: Don't fall over a stale temp file.Gravatar Joey Hess2011-11-17
|
* analysis; not a bug but a featureGravatar Joey Hess2011-11-17
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2011-11-17
|\
* | fix typo introduced with the Ref typeGravatar Joey Hess2011-11-17
| |
| * (no commit message)Gravatar https://www.google.com/accounts/o8/id?id=AItOawnBJ6Dv1glxzzi4qIzGFNa6F-mfHIvv9Ck2011-11-17
| |
| * (no commit message)Gravatar https://www.google.com/accounts/o8/id?id=AItOawnBJ6Dv1glxzzi4qIzGFNa6F-mfHIvv9Ck2011-11-17
| |
* | ensure branch exists before trying to update itGravatar Joey Hess2011-11-16
|/ | | | | | The branch may not exist, if .git/annex has been copied over from another repo (or a corrupted repo). I suppose it could also have gotten deleted somehow. Without this, there is a confusing failure.
* clarifyGravatar Joey Hess2011-11-16
|
* improve type signatures with a Ref newtypeGravatar Joey Hess2011-11-16
| | | | | | | | | | | In git, a Ref can be a Sha, or a Branch, or a Tag. I added type aliases for those. Note that this does not prevent mixing up of eg, refs and branches at the type level. Since git really doesn't care, except rare cases like git update-ref, or git tag -d, that seems ok for now. There's also a tree-ish, but let's just use Ref for it. A given Sha or Ref may or may not be a tree-ish, depending on the object type, so there seems no point in trying to represent it at the type level.
* better nameGravatar Joey Hess2011-11-16
|
* When not run in a git repository, git-annex can still display a usage ↵Gravatar Joey Hess2011-11-16
| | | | | | | message, and "git annex version" even works. Things that sound simple, but are made hard by the Annex monad being built with the assumption that there will always be a git repo.
* cleanupGravatar Joey Hess2011-11-16
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2011-11-16
|\
* | fix display of semitrusted repos in statusGravatar Joey Hess2011-11-16
| | | | | | | | | | | | semitrusted uuids rarely are listed in trust.log, so a special case is needed to get a list of them. Take the difference of all known uuids with non-semitrusted uuids.
* | cleanupGravatar Joey Hess2011-11-15
| |
* | merge: Now runs in constant space.Gravatar Joey Hess2011-11-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before, a merge was first calculated, by running various actions that called git and built up a list of lines, which were at the end sent to git update-index. This necessarily used space proportional to the size of the diff between the trees being merged. Now, lines are streamed into git update-index from each of the actions in turn. Runtime size of git-annex merge when merging 50000 location log files drops from around 100 mb to a constant 4 mb. Presumably it runs quite a lot faster, too.
| * Added a commentGravatar https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo2011-11-16
| |
| * (no commit message)Gravatar https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo2011-11-16
| |
* | cleanupGravatar Joey Hess2011-11-15
| |
* | avoid space leak writing mergeGravatar Joey Hess2011-11-15
|/ | | | | | | | | | | | | | | | | | This reduces the memory use of a merge by 1/3rd. The space leak was apparently because the whole update-index input was generated strictly, not lazily. I wondered if the change to ByteStrings contributed to this, due to the need to convert with L.pack here. But going back to the old code, I still see a much similar leak, and worse performance besides due to it not using ByteStrings. The fix is to just hPutStr the lines repeatedly. (Note the \0 is written separately, to avoid allocation overheads in adding it to the string.) The Git.pipeWrite interface is probably just wrong for any large inputs to git. This was the only place using it for input of any size. There is still at least one other space leak in the merge code.
* better error messageGravatar Joey Hess2011-11-15
|
* further insteadOf fixGravatar Joey Hess2011-11-15
|
* Fix support for insteadOf url remapping. Closes: #644278Gravatar Joey Hess2011-11-15
|
* close as resolvedGravatar Joey Hess2011-11-15
|
* removedGravatar http://cgray.myopenid.com/2011-11-15
|
* Added a commentGravatar http://cgray.myopenid.com/2011-11-15
|
* Added a commentGravatar http://cgray.myopenid.com/2011-11-15
|
* Added a commentGravatar http://joey.kitenet.net/2011-11-15
|
* Added a commentGravatar http://joey.kitenet.net/2011-11-15
|