| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
- some changes to the css and to the html layout
|
| |
|
| |
|
|
|
|
| |
Implemented the creation of the index for active and inactive bugs, with detail for earch of them
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Creation of the index file
|
|
|
|
| |
Following Ben's Wed, 01 Jul 2009 11:31:51 +1000 suggestion.
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Previously it choked when options.content_type == None.
I'm not sure how that made it past test_usage.sh...
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| | |
Loading all the bugs for the list search had the side effect of
updating all the bug values files to the new YAML format.
|
| |
| |
| |
| |
| | |
Now you can limit your list to bugs matching certain extra strings,
e.g. "TAG:working".
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| | |
Oops, I forgot to add becommands/tag.py with my last commit. Here it
is now, with the added ability to remove tags.
|
| |
| |
| |
| |
| |
| | |
And avoid confusion with bugs who's shorname is `list'? ;)
Now the usage info and help string also reflect the new method.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Since
<creator>John Doe <jdoe@example.com></creator>
is not valid XML.
|
|/
|
|
| |
Following Chris' advice. Don't know what I was thinking before ;).
|
| |
|
|
|
| |
$ be list --invalid-option | be comment <bug-id> -
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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 ;).
|
| | |
|
| |
| |
| |
| |
| | |
The new setting is currently only used when creating new bugs with
becommand/new.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
becommands/severity gets the configured settings appropriately.
Todo:
adjust setting-validation to compare against the current values.
setup becommands/severity to --complete severities.
|
| |
| |
| |
| |
| |
| |
| | |
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...
|
| |
| |
| |
| | |
Closes e2f6514c-5f9f-4734-a537-daf3fbe7e9a0
|
| | |
|
| | |
|
| | |
|