On Fri, 27 Oct 2006, A. Costa wrote:
> On Thu, 26 Oct 2006 22:58:18 -0700 Don Armstrong <[EMAIL PROTECTED]> wrote:
> > > If I'd missed an emailed reopen 'ack', it should be on the BTS page
> > > for #394813 somewhere...
> > 
> > The acks don't show up on the BTS; all you see is the effect of the
> > message to control, which is there:
> > 
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=394813#13
> 
> I'd received that and also seen it on the BTS, but as you say
> there's no reopen 'ack', just a "you closed it" message.

The message above *is* the reopen indication; you got sent an ack from
parsing that control mail.

> Some form of distinct reopen 'ack' would be less confusing.

The ack gets sent to you, not to the bug log. All the bug log gets is
the indication that the bug was reopened by your control message.

> To recap, a suggested fix would be one of these:
> 
>       1) Make the BTS smarter about emails. A 'reopen' and a '-done'
>          in one message could be parsed, and the BTS would consider
>          these contradictory orders, refuse to do either, then email
>          the user an error message explaining how one can't open and
>          close a bug simultaneously.

That's not going to happen. Because the messages are two separate
ones, one to -done, and one to control, the first message to control
actually opens the bug. It has no idea whether a message actually was
sent to -done or if it's just the To: headers lying.

The control message gets handled first, reopening the bug. Then the
done messages get handled, which close the bug. This is perfectly
consistent.
 
>       2) When a bug is reopened, the BTS would the user a clear
>       acknowledgement, -- prior to and separate from any closing
>       message.

This is done. If you didn't see it, you either missed it or your mail
system ate it.

>       3) When the BTS gets a reopen/close message, it processes it,
>          and the user is sent a message that it reopened/closed it
>          (that is two messages in one email instead of two separate
>          emails).

They're separate parsers; they have to be done separately.


Don Armstrong

-- 
Nothing is as inevitable as a mistake whose time has come.
 -- Tussman's Law

http://www.donarmstrong.com              http://rzlab.ucr.edu


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to