At 08:21 AM 11/3/2002 -0500, Alan DeKok wrote:
[EMAIL PROTECTED] wrote:
Why? What would it gain us?
it would help people keeping track of the development without having
the hassle
of doing a cvs co everytime.
I'm not *opposed* to setting it up, but it's one more thing to
maintain, and
At 09:50 AM 11/4/2002 -0600, Chris Parker wrote:
At 08:21 AM 11/3/2002 -0500, Alan DeKok wrote:
I'm not *opposed* to setting it up, but it's one more thing to
maintain, and I don't see much in the way of volunteers to do
additional work.
Well, since I'm running the server hosting the
Hi Alan,
Quoting Alan DeKok [EMAIL PROTECTED]:
Why? What would it gain us?
it would help people keeping track of the development without having the hassle
of doing a cvs co everytime.
Furthermore, if something is being discussed on this list that refers to a
funtion or file that has not yet
Paul Hampson [EMAIL PROTECTED] wrote:
Why? What would it gain us?
The ability to go back and see when a markedly broken problem
(such as that kill(-1) thing from last week) was introduced
and what the _intention_ was.
http://www.freeradius.org/cvs-log/
Alan DeKok.
-
List
[EMAIL PROTECTED] wrote:
Why? What would it gain us?
it would help people keeping track of the development without having the hassle
of doing a cvs co everytime.
http://www.freeradius.org/cvs-log/
The daily changes to CVS are mailed to the freeradius-devel list,
and are archived on
Hi,
I was wondering if there are plans to operate a tool like
Chora (http://www.horde.org/) on the FreeRadius homepage.
Would be nice to have a browsable CVS tree.
Just an idea.
Emre
--
Emre Bastuz
[EMAIL PROTECTED] http://www.emre.de
UIN: 561260 PGP Key ID
Emre Bastuz [EMAIL PROTECTED] wrote:
I was wondering if there are plans to operate a tool like
Chora (http://www.horde.org/) on the FreeRadius homepage.
Would be nice to have a browsable CVS tree.
Why? What would it gain us?
Alan DeKok.
-
List info/subscribe/unsubscribe? See http
.
Would be nice to have a browsable CVS tree.
Why? What would it gain us?
The ability to go back and see when a markedly broken problem
(such as that kill(-1) thing from last week) was introduced
and what the _intention_ was.
Not much of a reason, I realise. But the question was asked
