aboutsummaryrefslogtreecommitdiffstats
path: root/libbe/command/severity.py
Commit message (Collapse)AuthorAgeFilesLines
* Ran update-copyright.py.W. Trevor King2012-10-161-1/+1
|
* Rewrite commands to use bugdirs instead of a single bugdir.W. Trevor King2012-08-291-5/+6
| | | | | | | The bulk of the work is in regard to XML, with new BugDir.xml and .from_xml methods to support the new <bugdir> entity. I also split the guts import_xml's ._run method into sub-methods to make the import logic more obvious.
* Ran update-copyright.py.W. Trevor King2012-02-161-10/+10
|
* Run update_copyright.py.W. Trevor King2011-05-251-0/+2
|
* Move Tim Guirgies' help for status/severity overrides to .W. Trevor King2011-05-251-14/+2
|
* Remove "be set" reference in favour of actual helpTim Guirgies2011-05-251-1/+13
| | | | | | | | Because "be set severity blah" does not actually work, referring users there to set custom severity levels is just cruel (I spent a half hour trying to figure out what I was doing wrong). Thus, it is much easier to, at least for now, state in the help message what they must do in order to get custom severities and statuses.
* Restructure severity help function to match statusTim Guirgies2011-05-251-11/+16
| | | | | | | | | | | | | | | The code structure was vastly different in severity.py to status.py, so I mostly copied the structure from there and adjusted it to suit severity. The structure in status.py looked (to me) cleaner, more organised, and easier to work with. Also, users are now referred by "be severity --help" to "be set --help", in a manner similar to "be status --help". For those that don't know that severity can be adjusted on a per repository basis, this seems extremely helpful. A similar message appears for status, but not here.
* Bumped to version 1.0.01.0.0Chris Ball2011-01-081-1/+1
|
* Ran update_copyright.py.W. Trevor King2010-10-211-1/+1
|
* Ran update_copyright.pyW. Trevor King2010-06-221-12/+13
|
* Updated copyright informationW. Trevor King2010-01-011-1/+1
|
* Added UserInterface and other improved abstractions for command handlingW. Trevor King2009-12-311-6/+8
|
* Fixed libbe.command.diff + ugly BugDir.duplicate_bugdir implementationW. Trevor King2009-12-151-1/+1
| | | | | | | | | | | | | | | | | | | | | duplicate_bugdir() works, but for the vcs backends, it could require shelling out for _every_ file read. This could, and probably will, be horribly slow. Still it works ;). I'm not sure what a better implementation would be. The old implementation checked out the entire earlier state into a temporary directory pros: single shell out, simple upgrade implementation cons: wouldn't work well for HTTP backens I think a good solution would run along the lines of the currently commented out code in duplicate_bugdir(), where a VersionedStorage.changed_since(revision) call would give you a list of changed files. diff could work off of that directly, without the need to generate a whole duplicate bugdir. I'm stuck on how to handle upgrades though... Also removed trailing whitespace from all python files.
* Transitioned status to Command-formatW. Trevor King2009-12-141-2/+3
|
* Transitioned severity to Command-format, also added Command._get_*()W. Trevor King2009-12-141-73/+62
| | | | | | | | | | | | | | The old .requires_* thing was rediculous. The new ._get_*() callbacks allow the caller to provide a means for getting the expensive structures, which the command can use, or not, as required. This will also make it easier to implement the completion callbacks. The callbacks should probably have matching .set_*() methods, to avoid the current cache tweaking cmd._storage = ... etc. But that can wait for now...
* Initial directory restructuring to clarify dependenciesW. Trevor King2009-12-071-0/+106