Date: Sat, 25 Jan 1997 15:42:12 -0700 (MST)
From: Marc Slemko <marcs@znep.com>
To: new-httpd@hyperreal.com
Subject: Re: cvs commit: apache/src CHANGES mod_userdir.c
In-Reply-To: <199701252221.RAA00340@shado.jaguNET.com>
Message-ID: <Pine.BSF.3.95.970125153120.21048S-100000@alive.ampr.ab.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@hyperreal.com

http://dev.apache.org/private/bugdb.cgi

You need a password and login to access it; you have one, even if you may
not remember it.  

To display a list of bugs, just search the database without entering any
search text.

To display a particular bug number rewrite to CGI to let you do that.

If a report is "yours" to deal with claim ownership of it by modifying the
responsible person.  Then every once in a while review all the PRs you own
to be sure they aren't getting stale.

If a problem gets fixed, close it and note the revision number the file
was fixed in and what the next release/beta is that it will be fixed in.

When things are actually going to it (hint, hint Brian <g>), subscribe to
apache-bugdb to get a list of changes as they happen. 

I would like it if it could be accessed from the command line on taz, but
it can't really right now.  (reads can with query-pr but editing is a
different matter)

On Sat, 25 Jan 1997, Jim Jagielski wrote:

> Marc Slemko wrote:
> > 
> > Now that we are starting to use a bugs database, it would be a Good
> > Thing(tm) if you include a note saying "closes PR#666" in the commit
> > message.  Then it would be cool to actually close it.  <g>
> > 
> 
> *sheepish grin*
> 
> What's involved in using gnats? I clean forgot we even had it.
> -- 
> ====================================================================
>       Jim Jagielski            |       jaguNET Access Services
>      jim@jaguNET.com           |       http://www.jaguNET.com/
>                   "Not the Craw... the CRAW!"
>