On Tue, 10 Jan 2012 08:21:10 +0100, Mattias Backman
wrote:
> On Mon, Jan 9, 2012 at 2:45 PM, Tony Mansson wrote:
> > Hi Guys.
> >
> > I get a lot of spam from launchpad whenever the format of a blueprint is not
> > OK.
> >
> > Below is an example. Please don't use colons (as e.g. in an URL) insi
On 10 January 2012 11:50, Tony Mansson wrote:
> Hm, not according to the documentation:
>
> "The start is indicated by a line "Work items:" (anywhere in the
> whiteboard), then exactly one line for each work item, and finally an
> empty line to end the work item list. Each work item is one line wi
Hm, not according to the documentation:
"The start is indicated by a line "Work items:" (anywhere in the
whiteboard), then exactly one line for each work item, and finally an
empty line to end the work item list. Each work item is one line with
the description, then a colon, and the status, and op
On Mon, Jan 9, 2012 at 2:45 PM, Tony Mansson wrote:
> Hi Guys.
>
> I get a lot of spam from launchpad whenever the format of a blueprint is not
> OK.
>
> Below is an example. Please don't use colons (as e.g. in an URL) inside work
> item definitions. There is a low-IQ parser somewhere that gets co
On 9 January 2012 15:45, Tony Mansson wrote:
> Hi Guys.
>
> I get a lot of spam from launchpad whenever the format of a blueprint is not
> OK.
>
> Below is an example. Please don't use colons (as e.g. in an URL) inside work
> item definitions. There is a low-IQ parser somewhere that gets confused
