mirror of
https://git.FreeBSD.org/src.git
synced 2024-12-24 11:29:10 +00:00
57e58c3aa7
things fixed in here, including the '-ko' vs. -A problem with remote cvs which caused all files with -ko to be resent each time (which is damn painful over a modem, I can tell you). It also found a heap of stray empty directories that should have been pruned with the -P flag to cvs update but were not for some reason. It also has the fully integrated rcs and diff, so no more fork/exec overheads for rcs,ci,patch,diff,etc. This means that it parses the control data in the rcs files only once rather than twice or more. If the 'cvs diff' vs. Index thing is going to be fixed for future patch compatability, this is the place to do it.
62 lines
2.7 KiB
Plaintext
62 lines
2.7 KiB
Plaintext
CVS Development Policies
|
|
|
|
This file, DEVEL-CVS, contains the policies by which the CVS
|
|
development group operates. Also see the HACKING file.
|
|
|
|
----------------------------------------------------------------------
|
|
Charter for the devel-cvs mailing list:
|
|
|
|
The CVS Developers' List <devel-cvs@cyclic.com> exists to help people
|
|
with access to the CVS source repository co-ordinate changes, make
|
|
releases, and administer the repository.
|
|
|
|
Everyone who has been given checkin access to the repository for the
|
|
CVS sources should read devel-cvs. Only those with checkin access may
|
|
send messages to the list.
|
|
|
|
The devel-cvs list may be used to discuss:
|
|
- administrivia regarding the CVS source repository and release
|
|
process, and
|
|
- changes and features intended for inclusion in the official CVS
|
|
release (either source code or documentation), which someone plans
|
|
to implement, or has implemented.
|
|
|
|
The devel-cvs list should not be used to discuss:
|
|
- changes or features to packages other than the CVS release
|
|
(e.g., related packages like tkCVS, RAD/CVS, or other groups'
|
|
distributions of CVS, like RCVS, etc.),
|
|
- changes which nobody has offered to implement, or
|
|
- the philosophy of CVS (as opposed to a specific change to CVS).
|
|
These topics should either go on info-cvs, or have a new mailing list
|
|
created for them.
|
|
|
|
The topic restrictions in this charter do not reflect the development
|
|
group's future plans for CVS; rather, they reflect a topic
|
|
classification which the group finds helpful.
|
|
|
|
----------------------------------------------------------------------
|
|
Policies regarding the CVS source repository:
|
|
|
|
By checking items into the repository, developers agree to permit
|
|
distribution of such items under the terms of the GNU Public License.
|
|
|
|
----------------------------------------------------------------------
|
|
Procedure for dealing with people who want to be developers:
|
|
|
|
People who want checkin access are first requested to send
|
|
patches and have them reviewed by a developer. If they submit some
|
|
good ones (preferably over a period of time, to demonstrate sustained
|
|
interest), then one of the developers can ask the devel-cvs mailing
|
|
list whether it is OK to make this person a developer (after first
|
|
sending the prospective developer a copy of this file and then having
|
|
the prospective developer say they want to be a developer). If there
|
|
are no objections, the person will be made a developer.
|
|
|
|
----------------------------------------------------------------------
|
|
Policy regarding checkout-only access:
|
|
|
|
Checkout-only access to the CVS repository is available to all, on an
|
|
anonymous basis (no need for registration or other complications).
|
|
The exact technical mechanisms by which it is available are not
|
|
covered by this policy.
|