summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* documentation/warning message update for future featureGravatar Joey Hess2011-09-23
|
* one more hlintGravatar Joey Hess2011-09-20
|
* go go gadget hlintGravatar Joey Hess2011-09-20
|
* pull out pure codeGravatar Joey Hess2011-09-20
|
* bugfixGravatar Joey Hess2011-09-20
| | | | | | Different keys can have the same size, so can't make a Set of the sizes. This version actually runs faster yet, too..
* status: Massively sped up; remove --fast mode.Gravatar Joey Hess2011-09-20
| | | | | | | | | | Using Sets is the right thing; they have constant size lookup like my SizeList, and logn insertation, which beats nub to death. Runs faster than --fast mode did before, and gives accurate counts. 13 seconds total runtime with a warm cache in a repository with 40 thousand keys.
* status: In --fast mode, all status info is displayed now; but some of it is ↵Gravatar Joey Hess2011-09-20
| | | | only approximate, and is marked as such.
* simplifyGravatar Joey Hess2011-09-20
|
* convert Token to have separate constructors for each peice of syntaxGravatar Joey Hess2011-09-20
|
* Added a commentGravatar http://joey.kitenet.net/2011-09-19
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2011-09-19
|\
| * Added a commentGravatar http://joey.kitenet.net/2011-09-19
| |
* | some of these are now doneGravatar Joey Hess2011-09-19
| |
| * Added a commentGravatar http://joey.kitenet.net/2011-09-19
|/
* typoGravatar Joey Hess2011-09-19
|
* tweakGravatar Joey Hess2011-09-19
|
* clarify wordingGravatar Joey Hess2011-09-19
|
* special case for --in .Gravatar Joey Hess2011-09-19
| | | | | | Do not need to check the location log in this case, can just check inAnnex. This is both an optimisation and perhaps a correctness measure (fsck --in . should fsck files even if the location log is damaged.)
* reorgGravatar Joey Hess2011-09-19
|
* golfGravatar Joey Hess2011-09-19
|
* refactorGravatar Joey Hess2011-09-18
|
* fix memory leakGravatar Joey Hess2011-09-18
| | | | | | | | | | | | | | | | filterM is not a good idea if you were streaming in a large list of files. Fixing this memory leak that I introduced earlier today was a PITA because to avoid the filterM, it's necessary to do the filtering only after building up the data structures like BackendFile, and that means each separate data structure needs it own function to apply the filter, at least in this naive implementation. There is also a minor performance regression, when using copy/drop/get/fsck with a filter, git is now asked to look up attributes for all files, since that now comes before the filter is applied. This is only a very minor thing, since getting the attributes is very fast and --exclude was probably not typically used to speed it up.
* golfing with curryGravatar Joey Hess2011-09-18
|
* probably better to error on unknown tokenGravatar Joey Hess2011-09-18
|
* update docsGravatar Joey Hess2011-09-18
|
* make find show files meeting limits, even when not presentGravatar Joey Hess2011-09-18
| | | | | | | | | find: Rather than only showing files whose contents are present, when used with --exclude --copies or --in, displays all files that match the specified conditions. Note that this is a behavior change for find --exclude! Old behavior can be gotten with find --in . --exclude=...
* --copies=N can be used to make git-annex only operate on files with the ↵Gravatar Joey Hess2011-09-18
| | | | | | specified number of copies. (And --not --copies=N for the inverse.)
* add --in limitGravatar Joey Hess2011-09-18
|
* rework annex-ignore handlingGravatar Joey Hess2011-09-18
| | | | | | | | Only one place need to filter the list of remotes for ignored remotes: keyPossibilities. Make the full list available to everything else. This allows getting rid of the special case handing for --from and --to to make ignored remotes not be ignored with those options.
* update man page for file matching optionsGravatar Joey Hess2011-09-18
| | | | (--in is not yet implemented)
* add --and --or --not -( and -)Gravatar Joey Hess2011-09-18
| | | | | | | | I dislike -( and -), but without using a different option parser, can't easily use bare parens. --and and --or will become more useful once there are more interesting limits than --exclude
* refactor --exclude to use Utility.MatcherGravatar Joey Hess2011-09-18
| | | | | This should change no behavior, but opens the poissibility to use the matcher for other sorts of limits on which files git-annex processes.
* add a value to match against to match and matchMGravatar Joey Hess2011-09-18
|
* move to UtilityGravatar Joey Hess2011-09-18
|
* convert to parameterized types, so the Operation can be any type the caller ↵Gravatar Joey Hess2011-09-18
| | | | | | needs Especially handy for running a match monadically.
* a generic matcherGravatar Joey Hess2011-09-18
|
* ideaGravatar Joey Hess2011-09-17
|
* add news item for git-annex 3.20110915Gravatar Joey Hess2011-09-17
|
* releasing version 3.201109153.20110915Gravatar Joey Hess2011-09-17
|
* grouped commands into related sectionsGravatar Joey Hess2011-09-15
|
* remove now unnecessary git commitsGravatar Joey Hess2011-09-15
|
* tweakGravatar Joey Hess2011-09-15
|
* remove command type definitionsGravatar Joey Hess2011-09-15
| | | | | | | These were a mistake, they make the type signatures harder to read and less flexible. The CommandSeek, CommandStart, CommandPerform, and CommandCleanup types were a good idea, but composing them with the parameters expected is going too far.
* move annex.numcopies parsing into withNumCopiesGravatar Joey Hess2011-09-15
|
* bugfix: drop and fsck did not honor --excludeGravatar Joey Hess2011-09-15
|
* wordingGravatar Joey Hess2011-09-15
|
* add error for move --autoGravatar Joey Hess2011-09-15
| | | | | | | | | | | | | | | It probably does not make sense to enable auto mode for move. I cannot think of a situation where it would make sense to try to use it. A hypothetical auto mode for move would only differ from a normal move in one case -- when both repositories have a file, move deletes it from one, and this reduces the number of copies. So an auto mode would either only let move work in that situation, or avoid removing the file in that situation, depending on the number of copies. This would be complex to implement, and is perhaps not a very obvious behavior. The error is a good thing to have, so users don't expect it to do something it does not.
* copy --autoGravatar Joey Hess2011-09-15
| | | | Only does copy when numcopies is not yet satisfied.
* document --auto all in one placeGravatar Joey Hess2011-09-15
|
* commentGravatar Joey Hess2011-09-15
|