| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Gitano's executables, in addition to being required for operation,
are intended to be examples of how to use the gitano library,
so rather than importing with require "gitano.patterns",
gitano should be imported and use gitano.patterns.
No changes to imports are made inside lib/gitano/
because this would cause an import loop.
|
|
|
|
|
|
|
| |
This has moved every pattern that wasn't obviously just for string manipulation
and has in the process of doing so reworked some logic
so that fewer distinct patterns are used,
and the repository path normalisation has been unified.
|
| |
|
|
|
|
|
|
| |
This is a massive unpleasant commit which does whitespace cleanup
and fixes indentation (including untabifying). Hopefully we won't
need to do this ever again, if we keep an eye on commits.
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Vanush "Misha" Paturyan <misha@cs.nuim.ie>
|
|
|
|
|
|
|
|
|
|
| |
Each `.in` file needs to load plugins in order to ensure that all requisite
functionality is available at all points during the lifetime of a Gitano
operation.
This is a largely mechanical delta.
Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
|
| |
|
| |
|
| |
|
|
|
|
| |
containing info about the user
|
| |
|
|
|