aboutsummaryrefslogtreecommitdiffstats
path: root/libbe/command
Commit message (Collapse)AuthorAgeFilesLines
* Ran update-copyright.py.W. Trevor King2012-02-1625-250/+250
|
* Fix my busted 1512c0e2a64e patch to libbe/util/encoding.py.W. Trevor King2011-11-131-1/+1
| | | | | | | | | | | | | | Some temporary changes to encoding.py seem to have been added to commit 1512c0e2a64e19c8d4e5697257a4df5ddd8bc727 Author: W. Trevor King <wking@drexel.edu> Date: Tue Nov 8 07:14:43 2011 -0500 by accident. The initial change came from discussions with Niall Douglas, during which I realized that "filesystem encoding" ususally means the encoding for the *path*, not the *contents*. To avoid further confusion I'd renamed `get_filesystem_encoding` to the less ambiguous `get_text_file_encoding`. This commit should complete the transition.
* Ran update_copyright.py.W. Trevor King2011-11-091-0/+1
|
* Add ImportError to UnknownCommand output in get_command doctest.W. Trevor King2011-07-301-0/+1
| | | | | | | | | | This catches the test result up after: Commit: 0d5c9c68e947617c9d073d5f19351bdd8f3866db Author: W. Trevor King <wking@drexel.edu> Date: Wed May 25 10:30:19 2011 -0400 Attach ImportError message to UnknownCommand to aid debugging.
* Raise UserError if summary is not given to `be commit`.W. Trevor King2011-05-251-0/+3
| | | | | | | | | If the user doesn't provide the summary on the command line, through stdin, or through editor_string, raise an error. This will generally happen with $ be commit (user doesn't enter any text in the editory)
* Attach ImportError message to UnknownCommand to aid debugging.W. Trevor King2011-05-251-3/+8
|
* Rework summary handling in `be commit`.W. Trevor King2011-05-251-6/+18
| | | | | | Now you can run `be commit` with no options and have the summary split off the body automatically. This should be more familiar to most VCS users.
* Run update_copyright.py.W. Trevor King2011-05-2524-11/+44
|
* Move Tim Guirgies' help for status/severity overrides to .W. Trevor King2011-05-253-35/+54
|
* Remove "be set" reference in favour of actual helpTim Guirgies2011-05-252-2/+32
| | | | | | | | 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.
* Teach be status --help to load per tree configTim Guirgies2011-05-251-0/+4
| | | | | | Again, there is discrepancy between severity.py and status.py. I thought this feature was extremely useful in severity.py and it should be put into status.py too.
* 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.
* Fix test_log_request (broken by commit 36699d82).W. Trevor King2011-05-111-1/+1
|
* Revive the UserError/UsageError distinctionW. Trevor King2011-05-022-6/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | UsageError was removed back in commit bf3d434b244c57556bec979acbc658c30eb58221 Author: W. Trevor King <wking@drexel.edu> Date: Sat Dec 12 00:31:55 2009 -0500 Added libbe.command.base (with Command class)... because the distinction between UsageError and UserError was unclear. I've brought it back to satisfy a request by Christian Heinrich: On Sun, May 01, 2011 at 02:52:13AM +0200, Christian Heinrich wrote: > 3.) Using wrong syntax should receive better help messages. > > Current: > > "be new" -> ERROR: > Missing required argument SUMMARY > > Should be: > > "be new" -> usage: be new [options] SUMMARY > ... He suggested we print the full option list as well, but I've decided to just print the usage summary and remind the user how to get the full help message if they want it.
* Add summary line to the Serve command.W. Trevor King2011-05-011-1/+6
| | | | Thanks to Christian Heinrich for pointing this out.
* "X or ''|e" -> "(X or '')|e" for proper escaping.W. Trevor King2011-04-171-7/+7
|
* Correct <tdata> -> <tbody> typo in `be html` templates.W. Trevor King2011-04-171-2/+2
|
* Ensure comment div ids start with a letter (per validator.w3.org).W. Trevor King2011-04-171-2/+2
|
* Correct <tbody> -> </tbody> typo in `be html` templates.W. Trevor King2011-04-171-1/+1
|
* Rework `be html` to use Jinja2 templates.W. Trevor King2011-04-171-558/+530
|
* Temporarily disable writing in `be new` to avoid repeated updates.W. Trevor King2011-04-161-0/+3
|
* Add --notify to `be serve`.W. Trevor King2011-04-161-3/+51
|
* Add --preserve-uuids to `be import-xml`.W. Trevor King2011-04-161-2/+4
|
* Centralize assigned processing in parse_assigned & add assigned test to New.W. Trevor King2011-04-162-12/+17
|
* Merge remote branch 'cooper/master'W. Trevor King2011-04-161-1/+20
|\
| * Add support for 'none' and '-' with --assigned like in `be assign`Andrew Cooper2011-03-291-1/+6
| |
| * Add options --status and --severity to `be new`Andrew Cooper2011-03-291-0/+14
| |
* | Fix bd->bugdir typo in import_xml.Valtteri Kokkoniemi2011-04-161-1/+1
|/
* Remove commented code from html.pyChris Ball2011-02-221-3/+0
|
* Left aligned the table cellsGianluca Montecchi2011-01-251-4/+4
|
* New html output for html commandGianluca Montecchi2011-01-241-53/+209
|
* Merge commit 'refs/merge-requests/3' of git://gitorious.org/be/beChris Ball2011-01-085-10/+17
|\
| * Respected all sorting criteria, not only the last.Robert Lehmann2010-11-261-1/+1
| |
| * Change status on assignment of open bugs.Robert Lehmann2010-11-261-0/+2
| | | | | | | | | | | | | | After a bug has been assigned from status `open' it is no longer eligible for that status as described: A working bug that has not been assigned to a developer.
| * Safeguard List._sort_bugs from accumulating values in its default parameters.Robert Lehmann2010-11-261-1/+3
| |
| * Use a clean getattr() instead of eval().Robert Lehmann2010-11-261-1/+1
| |
| * Exclude --complete from completion.Robert Lehmann2010-11-261-1/+2
| |
| * Provide context in comments editor.Robert Lehmann2010-11-211-3/+5
| |
| * Fix list --important to actually apply a filter.Robert Lehmann2010-11-141-4/+4
| |
* | Bumped to version 1.0.01.0.0Chris Ball2011-01-0825-25/+31
| |
* | Fix unittest for `be show` after 22dd202ff4c0a1893f6e9f4d2b6aa1d4da3bf728.W. Trevor King2010-12-061-3/+3
| |
* | Adjust `be show --xml` since changes to version_info after Bzr->Git migration.W. Trevor King2010-12-061-2/+1
|/
* Make dependency tree output respect --show-status/--show-summary flags.W. Trevor King2010-10-281-6/+6
|
* Move Filter, parse_status, and parse_severity from list to depend.W. Trevor King2010-10-282-67/+68
| | | | This breaks an import dependency cycle.
* libbe.command.depend now shares libbe.command.list's status/severity parsing ↵W. Trevor King2010-10-282-38/+35
| | | | for consistency.
* Fixed `list --sort ...` bug.W. Trevor King2010-10-281-1/+3
|
* Add `list --sort time` test reproducing Gianluca's bug.W. Trevor King2010-10-281-0/+1
|
* Ran update_copyright.py.W. Trevor King2010-10-216-4/+6
|
* Default to "unknown" version info if libbe._version is missing.W. Trevor King2010-09-051-2/+1
|
* Fix "no attribute '_get_bugdir'" bug in `be help severity`.Marien Zwart2010-08-101-0/+1
| | | | | | | | | | | | | | | | | | | | | | | Bug and patch submitted by Marien Zwart. I can't think of any side effect issues this might raise, so I'm committing it ;). Excerpts from Marien's email below. From: Marien Zwart <...> Date: Tue, 10 Aug 2010 17:45:06 +0200 Subject: [Be-devel] "be help severity" fails (traceback) ... In current git (d63ec5fd3eca61ea53d06a96bfb52170111fc25d) "be help severity" produces the following: Traceback (most recent call last): ... AttributeError: 'Severity' object has no attribute '_get_bugdir' ... but I am not sure if this has any unintended side effects, so I'd prefer not to submit this as a merge request (for someone more familiar with the code to fix this instead). ...