[987] in Moira
the moiradev repository
daemon@ATHENA.MIT.EDU (Dan Winship)
Sun Jul 14 15:48:44 1996
Date: Sun, 14 Jul 1996 15:48:38 -0400 (EDT)
From: danw@MIT.EDU (Dan Winship)
To: moiradev@MIT.EDU
How to check sources out of the moiradev repository (the 1 minute
explanation... ask me or Jonathon or Ted or Greg if you need to do
something more complicated. Or try the `cvs' menu in emacs19's info
tree.)
setenv CVSROOT /afs/athena/astaff/project/moiradev/repository
(or just ~moiradev/repository if you use SIPB tcsh. You can do just
/mit/moiradev/repository if you want, but that will mean you have to
have moiradev attached whenever you do CVS operations on your working
directory)
cvs co moira
OR cvs co -d foo moira
to check it out into a directory named `foo' instead of moira
OR cvs co moira/clients
to check out just the clients (or some other subdir)
OR cvs co -r OPSSRC moira
to check out the OPSSRC branch
or some combination of those options. This will make your own copy of
the repository. (In CVS, you always work on your own copy of the
sources, never the ones in ~moiradev/src, which can be thought of as
read-only.)
Then, hack on the files for a while, and when you're done, do:
cvs ci
in the top-level directory you checked out, and it will find all of
your changes, and ask you for logs, and merge them in. If it has
problems merging them (most likely because someone else has also
checked in changes in that time), it will warn you, and then it will
put big <<<< and ==== and >>>> markers in the file to show you the
difference between what you had and what the other person had, and you
have to figure out how to merge them by hand. But again, this will
only happen if you and someone else are hacking the same file during
the same period of time.
-- Dan
PS - for now at least, the RCSed sources are still in
~moiradev/src.old.
