httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: STATUS in apachen
Date Sun, 21 Dec 1997 01:50:32 GMT
Rodent of Unusual Size wrote:
> 
> Erm, is it too late?  I'd like to suggest that STATUS be kept in
> apache-devsite rather than apachen.  Aside from not adding another
> step to how-to-release, that seems to be a more natural place for
> it anyway.  I would prefer that INDENT had been put there, too.
> 
> Does anyone object to putting project meta-activity files there
> rather than in the development tree itself?
> 
> I realise this can confuse things with the 1.2 work as well; I
> suggest STATUS-1.2.txt, STATUS-1.3.txt, and STATUS-2.0.txt under
> apache-devsite so they don't clutter the source tree, and can
> be readily viewed from a browser.
> 

Hmmm... I like the idea of it being available via web, but I
also like STATUS being in apachen since that's where the code
is that it refers to... thus a commit in apachen can take care
of it all.

I'm flexible though...

-- 
====================================================================
      Jim Jagielski            |       jaguNET Access Services
     jim@jaguNET.com           |       http://www.jaguNET.com/
            "Look at me! I'm wearing a cardboard belt!"

Mime
View raw message