aboutsummaryrefslogtreecommitdiffstats
path: root/becommands
Commit message (Collapse)AuthorAgeFilesLines
* Merged some bugfixes from be.wtk-rrW. Trevor King2009-07-181-0/+1
|\
| * Import sys in becommands/new.py.W. Trevor King2009-07-181-0/+1
| | | | | | | | Required for reading the bug summary string from stdin.
* | Renamed test->manipulate_encodings in becommands.*.execute.W. Trevor King2009-07-1618-90/+110
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Reminder from my initial libbe/encoding.py commit: Because of the stdout replacement, the doctests executes now need an optional 'test' argument to turn off replacement during the doctests, otherwise doctest flips out (since it had set up stdout to catch output, and then we clobbered it's setup). I'm also trying to catch stdout/stderr from be-handle-mail, and I ran into the same problem. It took me a bit to remember exactly what "test" was supposed to do, so I thought I'd make the argument name more specific. If you need other changes when running in "test" mode, you'll have to add other kwargs.
* | Added --author and --alt-id to "be comment".W. Trevor King2009-07-141-0/+8
|/ | | | | You could already add this info via the --xml input, now you can do it from the command line too.
* Updated GPLv2 to current GPLv2.W. Trevor King2009-07-1418-199/+198
| | | | | | | | | | | | | | | | | | | | | | | | Fixes Ben's bug 00f26f04-9202-4288-8744-b29abc2342d6. I also tweaked update_copyright.sh to make possible future copyright-blurb revision easier. The new algorithm is greedier, overwriting _all_ consecutive comments after a '^# Copyright' line, so do # Copyright # GPL ... GPL ... GPL # Your comment here... not # Copyright # GPL ... GPL ... GPL # # Your comment here... Without the blank line, your comment would get overwritten by the next run of update_copyright.sh. Note that catmutt is ignored by update_copyright.sh because Moritz Barsnick has only licensed his grepm code under the GPLv2 (not GPLv>=2). See the initial catmutt commit for details.
* Added "be comment --xml --ignore-missing-references ID COMMENT".W. Trevor King2009-07-121-1/+8
| | | | Now you don't have to edit them out by hand.
* Altered be-xml-to-mbox to work with non-ASCII input.W. Trevor King2009-07-121-1/+2
| | | | | | Now it runs off xml.etree instead of xml.sax. Removed "No matching bugs found" from "be list --xml" output.
* Not escaping whitespace (e.g. endlines) outside the XML document root.W. Trevor King2009-07-121-1/+1
| | | | | | ElementTree.XML was choking on them. I should unescape all whitespace (e.g. tabs, etc.), but I'm lazy and don't have any XML that's strange enough to need it ;).
* Added be-mbox-to-xml.W. Trevor King2009-07-122-2/+5
| | | | | | | | | | | | | | | | | | | | | | | Reworked to allow "be comment" to handle unicode strings (see bug e4ed63f6-9000-4d0b-98c3-487269140141). The solution was to escape all the unicode to produce and ASCII string before calling ElementTree.XML, and then converting back to unicode afterwards. Added a unicode-containing comment to the end of bug f7ccd916-b5c7-4890-a2e3-8c8ace17ae3a so that there's a handy unicode comment for testing. XML headers (e.g. '<?xml version="1.0" encoding="UTF-8" ?>') are now added to all xml output from be. Switched non-text/* encoding library to base64 instead of email.encoders, which makes that code in libbe/comment.py simpler. Changed libbe/mapfile.py error encoding from string_escape to unicode_escape so it can handle unicode. Everything's still untested, and be-xml-to-mbox doesn't handle unicode yet, but I felt this commit was getting a bit unwieldy ;).
* Went through "closed" bugs looking for miss-categorized bugs.W. Trevor King2009-07-111-3/+3
| | | | | | Found a few that were actually "fixed" and one that I reopened. Perhaps we should add a "merged" status to the default, so that the merged bugs don't clutter up the closed bugs category...
* Updating "be set --help" and "be status --help".W. Trevor King2009-07-112-20/+57
| | | | | | | | | I don't really like the "defaults to None" for the settings that have funky initialization procedures (most of them :p), but I'm not sure how to handle that cleanly yet. Perhaps be set --current I also need to find a method of adding complicated settings like the nested lists for severities, etc from the "be set" commandline.
* Removed <abentley@panoramicfeedback.com> from copyright blurbs.W. Trevor King2009-07-1114-14/+0
| | | | | | | | | | | These didn't work with my update_copyright.sh. I went with Aaron Bentley and Panometrics, Inc. instead of Aaron Bentley <abentley@panoramicfeedback.com> and Panometrics, Inc. just because of line length, but I'm open to convincing if people prefer the latter...
* "be comment --xml" now translates comment uuids to alt_ids.W. Trevor King2009-07-111-5/+11
|
* Adjustments to new versioned_property behavior.W. Trevor King2009-07-115-12/+12
| | | | | Also adjusted libbe/comment.py to move to user-specified alt_ids, rather than uuids.
* seems to work ;)W. Trevor King2009-07-101-5/+38
|
* Save whole bugdir in becommands/tag.py.W. Trevor King2009-07-101-1/+1
| | | | | | | It doesn't matter now, but at some point Bugdir might implement some sort of repo-wide caching which would need to be saved. The BugDir.save() method should be intelligent enough to not save things that have not changed, so efficiency should not be effected either.
* Added new-bug-from-stdin to mirror comments-from-stdin.W. Trevor King2009-07-071-3/+8
|
* Added "be show --only-raw-body COMMENT-ID".W. Trevor King2009-07-061-1/+7
|
* Added ability to show individual comments with "be show".W. Trevor King2009-07-061-10/+30
|
* "be init [ROOTDIR]" -> "be init [--root ROOTDIR]"W. Trevor King2009-07-011-15/+16
| | | | Following Ben's Wed, 01 Jul 2009 11:31:51 +1000 suggestion.
* Updated copyright blurbs and AUTHORS and included script for future updatesW. Trevor King2009-07-0116-16/+51
|
* "be set-root" changed to "be init"W. Trevor King2009-06-301-2/+2
| | | | | | | | | On the advice of Martin F Krafft <madduck@debian.org> as posted in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477125 on Fri, 12 Jun 2009 17:03:02 +0200
* "be comment" now handles the default options.content_type.W. Trevor King2009-06-301-1/+2
| | | | | Previously it choked when options.content_type == None. I'm not sure how that made it past test_usage.sh...
* Add "--show-status" flag to "be depend"W. Trevor King2009-06-301-1/+13
|
* Added ability to handle non text/* MIME types.W. Trevor King2009-06-261-3/+7
| | | | | | | | | | | | | | | | The main problem was the encoding/decoding that was happening to _all_ input/output. Now many I/O activities have a `binary' option to disable any encoding/decoding. The `binary' flag is set whenever the comment content-type is not a text/* type. In order to print valid XML (and make life easy on xml/be-xml-to-mbox), non text/* types are printed out as base64-encoded MIME messages, so be list --xml | be-xml-to-mbox | catmutt works as you'd expect. With the standard (non-XML) output from `be show', we just print a message telling the user that we can't reasonably display the MIME type and that they should use the XML output if they want to see it.
* Updated help strings, man page, and completionsW. Trevor King2009-06-252-2/+2
|
* Remove blank line from tag's output if no tags existW. Trevor King2009-06-251-1/+2
|
* Added regexp matching to `be list --extra-strings'W. Trevor King2009-06-251-4/+8
|
* Merged extra-strings branch, adding be tag/depend.W. Trevor King2009-06-253-4/+227
|\
| * Added `be depend'.W. Trevor King2009-06-252-20/+97
| | | | | | | | | | | | | | | | This closes bug 7ec2c071-9630-42b0-b08a-9854616f9144. BE is now bug free ;). At least until the next commit :p. Writing depend.py turned up a few style points in tag.py which I also fixed.
| * Added `be tag --list' to list all tags.W. Trevor King2009-06-251-5/+21
| | | | | | | | | | Loading all the bugs for the list search had the side effect of updating all the bug values files to the new YAML format.
| * Added -e/--extra-strings option to `be list`W. Trevor King2009-06-251-4/+12
| | | | | | | | | | Now you can limit your list to bugs matching certain extra strings, e.g. "TAG:working".
| * tag --remove now returns bug.settings["extra_strings"] to EMPTY.W. Trevor King2009-06-251-4/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | extra_strings returns to a defaulting property from a cached/generator property, with the help of the new, mutable defaults. Lots of deepcopies avoid mutable default uncertainty too ;). And copy.deepcopy([]) should be pretty cheap. tag --remove had previously left settings["extra_strings"] as [], which polluted the bug's values file. Now the improved defaulting_property notices a return to the default [], and sets the internally stored value to EMPTY. I struggled with creating a more intuitive way to notice changes to extra_strings than the tmp = bug.extra_strings <work on tmp> bug.extra_strings = tmp but didn't have any luck. The problem seems to be that if you only hand out copies of your default, you don't have any pointers to what you handed out to check for changes. On the other hand, if you hand out your original default, any external changes will _change_ your original default. I suppose you could only hand out copies, but keep a list of all copies handed out, but that sounds like a disaster. Reassigning is easy enough.
| * Added becommands/tag.pyW. Trevor King2009-06-231-0/+118
| | | | | | | | | | Oops, I forgot to add becommands/tag.py with my last commit. Here it is now, with the added ability to remove tags.
* | `be target list` -> `be target --list` to standardize syntax.W. Trevor King2009-06-241-3/+13
| | | | | | | | | | | | And avoid confusion with bugs who's shorname is `list'? ;) Now the usage info and help string also reflect the new method.
* | Add ability to list all current targets.Gianluca Montecchi2009-06-241-0/+7
|/ | | | | | | | | | | | | | | | | | From his Wed, 24 Jun 2009 23:08:25 +0200 email to the list: Hello As I noted some time ago, there is not a way to list all the present targets in the current repository. At the time, Chris send me a patch to have this feature, but it still not merged in the last revision (314). So this is a patch for this feature to apply against revision 314. It is basically a port of the old Chris's patch. bye Gianluca
* Added `be list --sort *` for user-selectable sorting.W. Trevor King2009-06-223-8/+25
| | | | | | | | | | | Also added libbe.bug.cmp_last_modified, which handles part of 9ce2f015-8ea0-43a5-a03d-fc36f6d202fe. To do better we could extend the RCS framework. I also transcribed a few emails from the be-devel list onto their relavent bugs and closed a few bugs. Finally, I removed some left over InvalidValue cruft.
* Merged be-xml-to-mboxW. Trevor King2009-06-221-4/+1
|\
| * Escape XML strings.W. Trevor King2009-06-221-6/+3
| | | | | | | | | | | | Since <creator>John Doe <jdoe@example.com></creator> is not valid XML.
* | Replaced some doctest output with ellipses.W. Trevor King2009-06-212-24/+24
|/ | | | Following Chris' advice. Don't know what I was thinking before ;).
* Added --xml option to becommands/list.pyW. Trevor King2009-06-211-6/+13
|
* Added comments-from-stdin, so we can add tracebacks, e.g. withW. Trevor King2009-06-191-7/+14
| | | $ be list --invalid-option | be comment <bug-id> -
* Merged Thomas Habets 2009-01-07 XML output for "be show".W. Trevor King2009-06-191-4/+22
|\ | | | | | | | | | | | | | | | | | | | | | | I rewrote a few of his routines, e.g. generalizing Comment.string_thread to run a caller-specified method avoided the need for some duplicate code in Comment.xml_thread. There was also a reasonable reorganization of libbe.settings_object.versioned_property because the <in_reply_to> field of the Comment.xml output was giving me `-1' (= old settings_object.EMPTY) instead of None, even after I had set comm.in_reply_to to None. The rewritten versioned_property avoids the ambiguity of UNPRIMED vs EMPTY, and avoids the stupididy of my using EMPTY=-1 ;).
| * XML output for "be show"Thomas Habets2009-01-071-2/+7
| |
* | Added per-tree default assignee option.W. Trevor King2008-12-041-0/+6
| | | | | | | | | | The new setting is currently only used when creating new bugs with becommand/new.
* | becommands/severity and status now handle --complete appropriately.W. Trevor King2008-12-042-7/+51
| | | | | | | | | | | | | | | | | | | | I also disabled interspersed options and arguments in cmdutils.CmdOptionParser. See http://docs.python.org/library/optparse.html Now $ be severity xyz --complete returns available severities. It had previously returned --help --complete
* | Per-tree status levels working.W. Trevor King2008-12-042-13/+16
| |
* | Adjusted becommands/list.py to use current bug severities levels.W. Trevor King2008-12-041-21/+19
| |
* | Per-tree settings now passed into bug module.W. Trevor King2008-12-041-12/+13
| | | | | | | | | | | | | | | | becommands/severity gets the configured settings appropriately. Todo: adjust setting-validation to compare against the current values. setup becommands/severity to --complete severities.
* | Added per-tree configurable severities.W. Trevor King2008-12-043-4/+7
| | | | | | | | | | | | | | They currently have no effect, but you can see them with $ be set There's a lot of information in this one 'settings' variable. I think set will have to be specialized to handle arrays smoothly...
generated by cgit (git 2.34.1) at 2024-09-20 16:27:35 +0000