Date: Wed, 24 Feb 1999 13:19:47 -0500
Message-Id: <199902241819.NAA31160@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <m10FiSe-000S6uC@inti.gov.ar> (salvador@inti.gov.ar)
Subject: Re: djgpp in cvs
References:  <m10FiSe-000S6uC AT inti DOT gov DOT ar>
Reply-To: djgpp-workers AT delorie DOT com


> Will be possible to commit changes?

The setup allows for commits for users with non-anonymous accounts
(me, for example :) but I haven't decided how to decide who gets
accounts.  I want to make sure that the people who can commit directly
are people with a history of submitting good, clean patches that
required little or no modifications before I applied them.

In any case, I doubt I'd want more than a handful of such people, just
to keep it from getting too confusing until we settle on a good system
for managing change.

Meanwhile, developers can at least be assured that they (1) have the
latest sources, and (2) can make diffs that will apply cleanly.  You
can also use cvs to tell if/when your patches are applied.