RE: Bugs cannot be updated if they are archived?

[Drew Adams]

> > It was (and is) not clear to me what that means. Is it archived or
> > unarchived?
> 
> It's archived.

So you click the link "archived and unarchived reports" to see reports that are
archived? Not too clear.

Actually, it seems that clicking that link shows all bugs, but that initially
only the outstanding (or the unarchived?) bugs are shown. If so, that's
confusing. Searching initially will not show an archived bug, but searching the
same page after clicking the link shows it.

How about clearly separating the various categories, and making it possible to
show (and search) all reports or just the reports of certain categories?

> > What does archiving (or unarchiving) mean? 
> 
> Archiving means that the bug has been put in a separate location to
> avoid cluttering the main view.

Putting it on a separate page would be cleaner and clearer, IMO. Your "separate
location" seems to be on the same page, but hidden initially (?).

> Bugs that are closed and have been inactive for more than 28 days are
> archived.

Is `closed' then a superset of `archived'? Or does `archived' include some stuff
that is not `closed'?

> > The heading that it appears under on that "archived and unarchived
> > reports" page is "Resolved bugs - Normal bugs". What does "resolved"
> > mean?
> 
> Resolved means that it has been fixed.

Not in English, it doesn't. ;-) It means that something was decided about it (it
was settled conclusively in some way). Do you mean `fixed' or `closed'? It
sounds more like you mean `closed'.

> > I replied to a message that said that the bug had been fixed, by
> > stating that it was still not fixed. But that reply apparently never
> > affected the bug status.
> 
> The bug tracking system is not a full featured natural language
> processing system, nor has it attained sentience. Someone has to mark
> a bug as not being fixed. You can do this using the control interface
> to the bug reporting system, as I have done with this email.
> Otherwise, the human beings reading the mail has to do it.

I see. I thought that any followup email, especially from the bug filer, would
be sufficient to keep a bug open (or reopen it). It wasn't even obvious to me
that the bug was closed. I was simply continuing (I thought), the original
bug-report email thread.

> > Whatever the correct diagnosis of the tracker status and problems
> > might be, bug #119 has not been fixed, and it does not appear among
> > the Outstanding bugs.
> 
> So instead of filing more bugs, reopen the original bug with more
> information. See http://emacsbugs.donarmstrong.com/server-control for
> more information.

I would have, if I knew how. 

However, I've also been explicitly told to open a new bug for bugs that have
been closed but that might still present a problem - including for this bug, a
couple of hours ago! 

Whatever. I'm all for reopening an existing bug instead of just creating a new
pointer bug. Just tell me how.

I clicked that URL link in my mail client and got this message from my Web
browser:

 "Internet Explorer cannot download server-control from 
  emacsbugs.donarmstrong.com. Internet Explorer was not able
  to open this Internet site. The requested site is either
  unavailable or cannot be found. Please try again later."

Where can I find the instructions for reopening etc. bugs? Is there another URL,
which I might be able to get to?

Oh - I see - that the URL works in Google Chrome. So your site appears to be
limited to particular browsers (and excludes the most commonly used browser).

>From what I can gather from that page, all I would need to do, to reopen bug
119, is to put these lines in the body of an email that replies to the
bug-report thread (i.e. with the same subject line, containing "bug #119"):

reopen 119
stop

Is that correct? Or would I need to send that to address@hidden,
instead of just replying to a mail in the bug-report thread?