On Wed, 14 Mar 2007 10:15:31 +0100
Bas Wijnen <[EMAIL PROTECTED]> wrote:
> The reason I want to mark this in a computer-readable way (as opposed
> to a textual message to the report), is that that would allow
> programs to present lists of "fixable" bugs in a better way.
> Whenever I see lists of
On Wed, Mar 14, 2007 at 10:38:00AM +0100, Bas Wijnen wrote:
> On Wed, Mar 14, 2007 at 11:34:05AM +0100, Michael Koch wrote:
> > On Wed, Mar 14, 2007 at 10:15:31AM +0100, Bas Wijnen wrote:
> > > I have a bug (#406121), which I don't want to fix before the release (it's
> > > minor). Is there a way
On Wed, Mar 14, 2007 at 11:34:05AM +0100, Michael Koch wrote:
> On Wed, Mar 14, 2007 at 10:15:31AM +0100, Bas Wijnen wrote:
> > I have a bug (#406121), which I don't want to fix before the release (it's
> > minor). Is there a way to tag it as such? Or should I just add a message
> > to the report
On Wed, Mar 14, 2007 at 10:15:31AM +0100, Bas Wijnen wrote:
> Hello mentors,
>
> I have a bug (#406121), which I don't want to fix before the release (it's
> minor). Is there a way to tag it as such? Or should I just add a message to
> the report (I just did) and do nothing else?
>
> I'm just t
Hello mentors,
I have a bug (#406121), which I don't want to fix before the release (it's
minor). Is there a way to tag it as such? Or should I just add a message to
the report (I just did) and do nothing else?
I'm just thinking that I could mark it as blocked by some Etch-release
pseudo-bug (w
5 matches
Mail list logo