summaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAge
* Added a commentGravatar https://www.google.com/accounts/o8/id?id=AItOawnBJ6Dv1glxzzi4qIzGFNa6F-mfHIvv9Ck2011-11-22
|
* Added a commentGravatar http://joey.kitenet.net/2011-11-22
|
* Added a comment: Case sensitivityGravatar https://www.google.com/accounts/o8/id?id=AItOawnBJ6Dv1glxzzi4qIzGFNa6F-mfHIvv9Ck2011-11-22
|
* add news item for git-annex 3.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
|
* (no commit message)Gravatar https://www.google.com/accounts/o8/id?id=AItOawnBJ6Dv1glxzzi4qIzGFNa6F-mfHIvv9Ck2011-11-22
|
* (no commit message)Gravatar http://cgray.myopenid.com/2011-11-21
|
* responseGravatar Joey Hess2011-11-20
|
* (no commit message)Gravatar https://www.google.com/accounts/o8/id?id=AItOawnBJ6Dv1glxzzi4qIzGFNa6F-mfHIvv9Ck2011-11-18
|
* 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
|
* (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
|
* clarifyGravatar 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.
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2011-11-16
|\
* | cleanupGravatar Joey Hess2011-11-15
| |
| * 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
|/
* 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
|
* Fix typoGravatar http://cgray.myopenid.com/2011-11-15
|
* (no commit message)Gravatar http://cgray.myopenid.com/2011-11-15
|
* status --json --fast for escGravatar Joey Hess2011-11-14
| | | | | | * status: Fix --json mode (only the repository lists are currently displayed) * status: --fast is back
* Added a commentGravatar http://joey.kitenet.net/2011-11-14
|
* Added a commentGravatar http://joey.kitenet.net/2011-11-14
|
* (no commit message)Gravatar http://www.joachim-breitner.de/2011-11-14
|
* status: Now displays trusted, untrusted, and semitrusted repositories ↵Gravatar Joey Hess2011-11-14
| | | | separately.
* Optimised union merging; now only runs git cat-file once.Gravatar Joey Hess2011-11-12
|
* avoid unnecessary auto-merge when only changing a file in the branch.Gravatar Joey Hess2011-11-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | Avoids doing auto-merging in commands that don't need fully current information from the git-annex branch. In particular, git annex add no longer needs to auto-merge. Affected commands: Anything that doesn't look up data from the branch, but does write a change to it. It might seem counterintuitive that we can change a value without first making sure we have the current value. This optimisation works because these two sequences are equivilant: 1. pull from remote 2. union merge 3. read file from branch 4. modify file and write to branch vs. 1. read file from branch 2. modify file and write to branch 3. pull from remote 4. union merge After either sequence, the git-annex branch contains the same logical content for the modified file. (Possibly with lines in a different order or additional old lines of course).
* addGravatar Joey Hess2011-11-12
|
* addGravatar Joey Hess2011-11-12
|
* add news item for git-annex 3.20111111Gravatar Joey Hess2011-11-11
|
* map: Support remotes with /~/ and /~user/Gravatar Joey Hess2011-11-11
| | | | | | | | | | More accurately, it was supported already when map uses git-annex-shell, but not when it does not. Note that the user name cannot be shell escaped using git-annex's current approach for shell escaping. I tried and some shells like dash cannot cd ~'joey'. Rest of directory is still shell escaped, not for security but in case a directory has a space or other weird character.
* tested all known types of cycles, all are fixedGravatar Joey Hess2011-11-10
| | | | | My testing involved widening the race by adding sleeps, and making sure something sane happens in each case.
* exclusive locks, ughGravatar Joey Hess2011-11-09
|
* safer inannex checkingGravatar Joey Hess2011-11-09
| | | | | | | | git-annex-shell inannex now returns always 0, 1, or 100 (the last when it's unclear if content is currently in the index due to it currently being moved or dropped). (Actual locking code still not yet written.)
* reorg to allow taking content lockGravatar Joey Hess2011-11-09
| | | | | | | The lock will only persist during the perform stage, so the content must be removed from the annex then, rather than in the cleanup stage. (No lock is actually taken yet.)
* warning about version of git-annex shipped in recent Ubuntu releaseGravatar Joey Hess2011-11-09
|
* directly lock content?Gravatar Joey Hess2011-11-09
|
* problem that came to me at 2 amGravatar Joey Hess2011-11-09
|
* fixGravatar Joey Hess2011-11-08
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-09-22 05:33:40 +0000