You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Rodent of Unusual Size <Ke...@Golux.Com> on 2000/04/06 13:08:39 UTC
Re: cvs commit: apache-2.0 KEYS
marc@locus.apache.org wrote:
>
> marc 00/03/11 10:15:17
>
> Modified: . KEYS
> Log:
> Add my pgp key. Hmm. These files are awfully different.
Since the KEYS file is put in the distribution area, the
1.3 and 2.0 files need to be identical. It looks as though
the dist area currently has the 1.3 file, which means the
2.0a2 release can't be checked using its contents.
--
#ken P-)}
Ken Coar <http://Golux.Com/coar/>
Apache Software Foundation <http://www.apache.org/>
"Apache Server for Dummies" <http://Apache-Server.Com/>
"Apache Server Unleashed" <http://ApacheUnleashed.Com/>
Re: cvs commit: apache-2.0 KEYS
Posted by rb...@apache.org.
On Thu, 6 Apr 2000, Manoj Kasichainula wrote:
> On Thu, Apr 06, 2000 at 07:08:39AM -0400, Rodent of Unusual Size wrote:
> > Since the KEYS file is put in the distribution area, the
> > 1.3 and 2.0 files need to be identical. It looks as though
> > the dist area currently has the 1.3 file, which means the
> > 2.0a2 release can't be checked using its contents.
>
> How about moving the KEYS file to one of the site repositories (I'd
> lean towards asf-site), so that it's not duplicated?
I may be wrong, but I am 99% sure that the 2.0 KEYS file is the 1.3 file
plus my keys. Can we just move the 2.0 file to the dist directory, and
use it from now on?
Ryan
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
Re: cvs commit: apache-2.0 KEYS
Posted by Manoj Kasichainula <ma...@io.com>.
On Thu, Apr 06, 2000 at 07:08:39AM -0400, Rodent of Unusual Size wrote:
> Since the KEYS file is put in the distribution area, the
> 1.3 and 2.0 files need to be identical. It looks as though
> the dist area currently has the 1.3 file, which means the
> 2.0a2 release can't be checked using its contents.
How about moving the KEYS file to one of the site repositories (I'd
lean towards asf-site), so that it's not duplicated?