You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Marc Slemko <ma...@worldgate.com> on 1998/07/28 00:41:06 UTC

Re: cvs commit: apache-site bugdb.cgi

On 27 Jul 1998 coar@hyperreal.org wrote:

> coar        98/07/27 15:39:26
> 
>   Modified:    .        bugdb.cgi
>   Log:
>   	Change the default search state from "open" to "any".
>   
>   Revision  Changes    Path
>   1.32      +2 -1      apache-site/bugdb.cgi
>   
>   Index: bugdb.cgi
>   ===================================================================
>   RCS file: /export/home/cvs/apache-site/bugdb.cgi,v
>   retrieving revision 1.31
>   retrieving revision 1.32
>   diff -u -r1.31 -r1.32
>   --- bugdb.cgi	1998/05/28 10:56:55	1.31
>   +++ bugdb.cgi	1998/07/27 22:39:25	1.32
>   @@ -126,6 +126,7 @@
>    #    for editors without full domain names.
>    #  05/28/1998 Ken Coar - Change the 'still alive?' standard response to include
>    #    a request for retesting under the latest sotware.
>   +#  07/27/1998 Ken Coar - Change the default search state from "open" to "any".

I really don't know that it is necessary to maintain a list of every
little change in thefile; that is what CVS is for.


Re: cvs commit: apache-site bugdb.cgi

Posted by Marc Slemko <ma...@worldgate.com>.
On Tue, 28 Jul 1998, Rodent of Unusual Size wrote:

> Marc Slemko wrote:
> > 
> > I can say the exact same thing for anything distributed with Apache, and
> > the answer is the same: check the CVS logs and use diff.  Unless you are
> > hiding something from me, everyone has trivial access to the CVS history
> > for any file in multiple ways.
> 
> bugdb.cgi and libgnats.pl aren't distributed with Apache - they live only
> in apache-site.  I suppose interested parties can check the webcvs stuff;

Or anoncvs, or probably cvsup, etc.  Just like the rest of the source.

> that's a good point.  But what's the harm in the inline comments?  It's
> only one file.  In the environments where I've worked, it's appropriate
> to put mod histories both into the source and the CM logs - you never
> know when a snapshot is going to be taken or the CM system decommissioned
> or broken.


The harm is that it is only one file, it is completely different than
everything else that is done for no good resaon, and it looks a bit silly
to add more to the file in changelog than the tiny little change that was
done.

If you are truly worried about CVS magically going away over night, then
you have a lot bigger problems that adding a change history to one file
isn't going to solve.  

> 
> The CVS logs only help if the log messages actually make sense; there
> have been times when that's been problematical - such as blank lines
> or that silliness earlier this year with weather reports.  The latter
> was a special case, though. :-)

Erm... if there is nothing sensible to put as a log message then there is
no harm in not putting a useful message.  No one had better try such a
thing with a code change.

That is a bogus excuse.  "I need to enter change history in the file
because I can make bogus log messages when I commit."


Re: cvs commit: apache-site bugdb.cgi

Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
Marc Slemko wrote:
> 
> I can say the exact same thing for anything distributed with Apache, and
> the answer is the same: check the CVS logs and use diff.  Unless you are
> hiding something from me, everyone has trivial access to the CVS history
> for any file in multiple ways.

bugdb.cgi and libgnats.pl aren't distributed with Apache - they live only
in apache-site.  I suppose interested parties can check the webcvs stuff;
that's a good point.  But what's the harm in the inline comments?  It's
only one file.  In the environments where I've worked, it's appropriate
to put mod histories both into the source and the CM logs - you never
know when a snapshot is going to be taken or the CM system decommissioned
or broken.

The CVS logs only help if the log messages actually make sense; there
have been times when that's been problematical - such as blank lines
or that silliness earlier this year with weather reports.  The latter
was a special case, though. :-)

#ken	P-)}

Ken Coar                    <http://Web.Golux.Com/coar/>
Apache Group member         <http://www.apache.org/>
"Apache Server for Dummies" <http://WWW.Dummies.Com/


Re: cvs commit: apache-site bugdb.cgi

Posted by Marc Slemko <ma...@worldgate.com>.
I can say the exact same thing for anything distributed with Apache, and
the answer is the same: check the CVS logs and use diff.  Unless you are
hiding something from me, everyone has trivial access to the CVS history
for any file in multiple ways.

On Mon, 27 Jul 1998, Rodent of Unusual Size wrote:

> Marc Slemko wrote:
> > 
> > I really don't know that it is necessary to maintain a list of every
> > little change in thefile; that is what CVS is for.
> 
> What you don't see, Marc, is the number of requests that Brian and
> I get for the raw script.  Other groups are using it as a basis
> for *their* PR systems {shudder}, and they *don't* have access to
> the stuff in our CVS.  So if one of these chaps wants to check the
> version he got six months ago with what we've got online now, these
> one-line comments are very helpful.
> 
> #ken	P-)}
> 
> Ken Coar                    <http://Web.Golux.Com/coar/>
> Apache Group member         <http://www.apache.org/>
> "Apache Server for Dummies" <http://WWW.Dummies.Com/
> 


Re: cvs commit: apache-site bugdb.cgi

Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
Marc Slemko wrote:
> 
> I really don't know that it is necessary to maintain a list of every
> little change in thefile; that is what CVS is for.

What you don't see, Marc, is the number of requests that Brian and
I get for the raw script.  Other groups are using it as a basis
for *their* PR systems {shudder}, and they *don't* have access to
the stuff in our CVS.  So if one of these chaps wants to check the
version he got six months ago with what we've got online now, these
one-line comments are very helpful.

#ken	P-)}

Ken Coar                    <http://Web.Golux.Com/coar/>
Apache Group member         <http://www.apache.org/>
"Apache Server for Dummies" <http://WWW.Dummies.Com/