eb05416991
Taken from sources in CVS at:
https://sourceforge.net/projects/rocketworkbench/
Sources extracted in two steps:
1. Pull entire project tree into a subdir "rwb" via "rsync":
rsync -a a.cvs.sourceforge.net::cvsroot/rocketworkbench/ rwb/.
2. Export sources:
export CVSROOT=$(pwd)/rwb
SUBDIRS="analyser cpropep cpropep-web CVSROOT data libcompat libcpropep libnum libsimulation libthermo prop rocketworkbench rockflight"
mkdir rwbx; cd rwbx
cvs export -D now ${SUBDIRS}
After this (and some backups for safety), the directory content was
added to a Git repo:
git init .
git add *
22 lines
1.0 KiB
Plaintext
22 lines
1.0 KiB
Plaintext
# The "editinfo" file is used to allow verification of logging
|
|
# information. It works best when a template (as specified in the
|
|
# rcsinfo file) is provided for the logging procedure. Given a
|
|
# template with locations for, a bug-id number, a list of people who
|
|
# reviewed the code before it can be checked in, and an external
|
|
# process to catalog the differences that were code reviewed, the
|
|
# following test can be applied to the code:
|
|
#
|
|
# Making sure that the entered bug-id number is correct.
|
|
# Validating that the code that was reviewed is indeed the code being
|
|
# checked in (using the bug-id number or a seperate review
|
|
# number to identify this particular code set.).
|
|
#
|
|
# If any of the above test failed, then the commit would be aborted.
|
|
#
|
|
# Actions such as mailing a copy of the report to each reviewer are
|
|
# better handled by an entry in the loginfo file.
|
|
#
|
|
# One thing that should be noted is the the ALL keyword is not
|
|
# supported. There can be only one entry that matches a given
|
|
# repository.
|