Re: [Linuxdc-dev] CVS decision.

[<gh...@in...>]

On Sun, 31 Dec 2000, Rene Malmgren wrote:

> Well I an't Marcus. But in the meantime I thinkt we have to make due
> with my kernel...
> 
> I got tierd of waiting and pached up mine to a "workable" state.

Wonderful.

> How do I check it in?

Easiest way of doing it would be this:

cvs -d :ext:du...@cv...:/cvsroot/linuxdc co \
linux

Now you have the linux kernel tree that lies on SF. Copy/patch your
modifications into the checked out tree. (You might have already worked in
this tree. But it's imperative that you checked it out as your SF login
account, not as anonymous. If you checked it out as anonymous, you're not
allowed to check changes back in.)

After the patching, stay in the linux directory (the root directory of the
tree) and do:

cvs up

This will insure that if marcus or anybody else with cvs access (me ;)
have done any modifications, those modifications will be applied to your
local tree. Your local tree must be completely up to date before you do a
check in.

To check in, you have to do two things:

1) For all the new files that are not already in the tree, you must do
   cvs add <filename>
2) Once all those files have been added and the rest have been patched,
   do, from the linux-kernel root directory ('linux')
   cvs commit -m "First attempt at a bootable kernel"

The message is for you to decide. It's normal to have a specific message
for each file that you commit. That is, for each fix you do, you commit
the file you fixed with an appropriate comment. That way, we can easily
look at a file's revision history and see who and when fixed which bugs.

General comments such as that one I suggested above ("First attempt..")
should be used very seldom, since it really doesn't tell us what has been
fixed in the files that have been touched (patched).


I hope this helps. If there's any interest for it, I can look around and
see if there are any CVS guidelines we could adopt. If not, I could try
writing some, and put them up on our pages. It would be a Good Thing to
have some kind of guideline for how we mess up the tree.


Regards,

Karl T