On Sep 12, 3:08 pm, Jason Grout wrote:
> > Which features shall we ask the trac and wiki admins to install?
>
> For a long time, I've wanted a report of all tickets on which I've
> participated (i.e., commented, started, been assigned, posted patches, etc.)
>
> Jason
There is a trac ticket for
On Sun, Sep 20, 2009 at 4:02 PM, Pat LeSmithe wrote:
>
> William Stein wrote:
>> On Sat, Sep 12, 2009 at 2:27 PM, Pat LeSmithe wrote:
>>> Is there an easy way to test various macros and plug-ins short of a
>>> site-wide installation at Sage trac?
>>
>> Why don't you install trac and try out anyt
William Stein wrote:
> On Sat, Sep 12, 2009 at 2:27 PM, Pat LeSmithe wrote:
>> Is there an easy way to test various macros and plug-ins short of a
>> site-wide installation at Sage trac?
>
> Why don't you install trac and try out anything you want? It's not
> hard to install.
>
> There is an *
On Sat, Sep 12, 2009 at 2:27 PM, Pat LeSmithe wrote:
>
> On Sat, Sep 12, 2009 at 12:08 PM, Jason Grout
> wrote:
>> For a long time, I've wanted a report of all tickets on which I've
>> participated (i.e., commented, started, been assigned, posted patches, etc.)
>
> Unless I'm mistaken, with macr
On Sat, Sep 12, 2009 at 12:08 PM, Jason Grout
wrote:
> For a long time, I've wanted a report of all tickets on which I've
> participated (i.e., commented, started, been assigned, posted patches, etc.)
Unless I'm mistaken, with macros similar to these
http://trac-hacks.org/wiki/WikiTableMacro
ht
William Stein wrote:
> On Sat, Sep 12, 2009 at 12:08 PM, Jason Grout
> wrote:
>>
>>> Which features shall we ask the trac and wiki admins to install?
>>
>> For a long time, I've wanted a report of all tickets on which I've
>> participated (i.e., commented, started, been assigned, posted patches,
On Sat, Sep 12, 2009 at 12:08 PM, Jason Grout
wrote:
>
>
>> Which features shall we ask the trac and wiki admins to install?
>
>
> For a long time, I've wanted a report of all tickets on which I've
> participated (i.e., commented, started, been assigned, posted patches, etc.)
>
trac admins can c
> Which features shall we ask the trac and wiki admins to install?
For a long time, I've wanted a report of all tickets on which I've
participated (i.e., commented, started, been assigned, posted patches, etc.)
Jason
--
Jason Grout
--~--~-~--~~~---~--~~
To
William Stein wrote:
> On Fri, Sep 11, 2009 at 10:13 PM, Pat LeSmithe wrote:
>> Assuming the code
>> http://trac-hacks.org/svn/ticketbacklinksmacro/0.11/TicketBackLinksDescription/macro.py
>> actually works, I think we can tailor the SQL query to select records
>> from the "ticket" table.
>>
>> I
On Fri, Sep 11, 2009 at 10:13 PM, Pat LeSmithe wrote:
>
> Dan Drake wrote:
> > On Fri, 11 Sep 2009 at 07:02PM -0700, Pat LeSmithe wrote:
> >> Dan Drake wrote:
> >>> On Fri, 11 Sep 2009 at 03:39PM -0700, Pat LeSmithe wrote:
> Which features shall we ask the trac and wiki admins to install?
>
Dan Drake wrote:
> On Fri, 11 Sep 2009 at 07:02PM -0700, Pat LeSmithe wrote:
>> Dan Drake wrote:
>>> On Fri, 11 Sep 2009 at 03:39PM -0700, Pat LeSmithe wrote:
Which features shall we ask the trac and wiki admins to install?
>>> One feature I would like is forward references for tickets. This
On Fri, 11 Sep 2009 at 07:02PM -0700, Pat LeSmithe wrote:
> Dan Drake wrote:
> > On Fri, 11 Sep 2009 at 03:39PM -0700, Pat LeSmithe wrote:
> >> Which features shall we ask the trac and wiki admins to install?
> >
> > One feature I would like is forward references for tickets. This is a
> > bit lik
Dan Drake wrote:
> On Fri, 11 Sep 2009 at 03:39PM -0700, Pat LeSmithe wrote:
>> Which features shall we ask the trac and wiki admins to install?
>
> One feature I would like is forward references for tickets. This is a
> bit like the ticket dependency graph, but just for links. I'm imagining
> tw
On Fri, 11 Sep 2009 at 03:39PM -0700, Pat LeSmithe wrote:
> Which features shall we ask the trac and wiki admins to install?
One feature I would like is forward references for tickets. This is a
bit like the ticket dependency graph, but just for links. I'm imagining
two lists: "Ticket comments tha
William Stein wrote:
> On Fri, Sep 11, 2009 at 1:18 PM, Pat LeSmithe wrote:
>> William Stein wrote:
>>> On Fri, Sep 11, 2009 at 11:41 AM, Pat LeSmithe wrote:
To colorize code blocks in trac descriptions and comments, try
>>> Are you saying "Hey guys, here's a feature that is in trac already
William Stein wrote:
> On Fri, Sep 11, 2009 at 11:41 AM, Pat LeSmithe wrote:
>> To colorize code blocks in trac descriptions and comments, try
> Are you saying "Hey guys, here's a feature that is in trac already,
> but nobody seems to be using it. In order to use it, put #!python at
> the top of
On Fri, Sep 11, 2009 at 1:18 PM, Pat LeSmithe wrote:
>
> William Stein wrote:
>> On Fri, Sep 11, 2009 at 11:41 AM, Pat LeSmithe wrote:
>>> To colorize code blocks in trac descriptions and comments, try
>> Are you saying "Hey guys, here's a feature that is in trac already,
>> but nobody seems to
On Fri, Sep 11, 2009 at 11:41 AM, Pat LeSmithe wrote:
>
> To colorize code blocks in trac descriptions and comments, try
Are you saying "Hey guys, here's a feature that is in trac already,
but nobody seems to be using it. In order to use it, put #!python at
the top of your {{{ pre-formats? Oh,
18 matches
Mail list logo
