Re: [Flightgear-devel] CVS and branch development

2004-10-06 Thread Mathias Fröhlich
Hmm, Sorry about that. I had a quick look into the cvs commit logs at the time you asked. It turned out to be too quick ... On Dienstag 05 Oktober 2004 16:48, Jon Berndt wrote: Well, I've just about had it with cvs branches. I tagged some files in a branch, then moved to a test directory and

RE: [Flightgear-devel] CVS and branch development

2004-10-05 Thread Jon Berndt
How does one create a branch? I know how to tag changed files locally: cvs tag -b JSB_New_XML FGAircraft.cpp FGAircraft.h Is that what you mean? This is for creating a branch. Then you have to tell that you are working on it by doing : cvs update -r JSB_New_XML FGAircraft.cpp

RE: [Flightgear-devel] CVS and branch development

2004-10-05 Thread Frederic Bouvier
Jon Berndt wrote : How does one create a branch? I know how to tag changed files locally: cvs tag -b JSB_New_XML FGAircraft.cpp FGAircraft.h Is that what you mean? This is for creating a branch. Then you have to tell that you are working on it by doing : cvs update -r

RE: [Flightgear-devel] CVS and branch development

2004-10-05 Thread Jon Berndt
Well, I've just about had it with cvs branches. I tagged some files in a branch, then moved to a test directory and checked out that branch, but only got the branch-tagged files. I needed all of the files, except I wanted the updated files on the specified branch. One thing that makes this

RE: [Flightgear-devel] CVS and branch development

2004-10-05 Thread Frederic Bouvier
Jon Berndt wrote: Well, I've just about had it with cvs branches. I tagged some files in a branch, then moved to a test directory and checked out that branch, but only got the branch-tagged files. I needed all of the files, except I wanted the updated files on the specified branch. use

RE: [Flightgear-devel] CVS and branch development

2004-10-05 Thread Frederic Bouvier
I incorrectly wrote: If I where you, ... Oops, bad english: I meant 'If I was you, ...' -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d

RE: [Flightgear-devel] CVS and branch development

2004-10-05 Thread Jon Berndt
If I where you, I would tag the whole tree so that I wouldn't have to remember what are files that need to be in the branch and those that are not. cvs do a good job when adding or removing solely in the branch. Sounds like a good idea. Jon ___

RE: [Flightgear-devel] CVS and branch development

2004-10-04 Thread Jon Berndt
Just for the record: - Creating that new branch. How does one create a branch? I know how to tag changed files locally: cvs tag -b JSB_New_XML FGAircraft.cpp FGAircraft.h Is that what you mean? jon ___ Flightgear-devel mailing list [EMAIL

RE: [Flightgear-devel] CVS and branch development

2004-10-04 Thread Jon Berndt
Hi Jon, On Sonntag 03 Oktober 2004 16:06, Jon Berndt wrote: I am trying to save to JSBSim CVS some files I have modified for reading the new JSBSim XML format. These files should not be part of the main (HEAD) branch at the moment. I'm not sure I have done this correctly. Can a CVS

Re: [Flightgear-devel] CVS and branch development

2004-10-04 Thread Frederic Bouvier
Jon Berndt wrote: Just for the record: - Creating that new branch. How does one create a branch? I know how to tag changed files locally: cvs tag -b JSB_New_XML FGAircraft.cpp FGAircraft.h Is that what you mean? This is for creating a branch. Then you have to tell that you are

RE: [Flightgear-devel] CVS and branch development

2004-10-04 Thread Jon Berndt
Just for the record: - Creating that new branch. How does one create a branch? I know how to tag changed files locally: cvs tag -b JSB_New_XML FGAircraft.cpp FGAircraft.h Is that what you mean? This is for creating a branch. Then you have to tell that you are working on

Re: [Flightgear-devel] CVS and branch development

2004-10-04 Thread Frederic Bouvier
Jon Berndt wrote: Just for the record: - Creating that new branch. How does one create a branch? I know how to tag changed files locally: cvs tag -b JSB_New_XML FGAircraft.cpp FGAircraft.h Is that what you mean? This is for creating a branch. Then you have to tell

Re: [Flightgear-devel] CVS and branch development

2004-10-04 Thread Arnt Karlsen
On Mon, 4 Oct 2004 16:47:12 +0200, Frederic wrote in message [EMAIL PROTECTED]: Jon Berndt wrote: Just for the record: - Creating that new branch. How does one create a branch? I know how to tag changed files locally: cvs tag -b JSB_New_XML FGAircraft.cpp

Re: [Flightgear-devel] CVS and branch development

2004-10-04 Thread Frederic Bouvier
Arnt Karlsen wrote: On Mon, 4 Oct 2004 16:47:12 +0200, Frederic wrote in message [EMAIL PROTECTED]: Jon Berndt wrote: Just for the record: - Creating that new branch. How does one create a branch? I know how to tag changed files locally: cvs tag -b

RE: [Flightgear-devel] CVS and branch development

2004-10-04 Thread Jon Berndt
..meanwhile, is there a go-away flag that can be set to prevent us mortals and not from cvs co'ing known bad code trees? No because this repository is located at Sourceforge and there is no way to shutdown the repository during this maintenance operation. -Fred I'll try and get this

Re: [Flightgear-devel] CVS and branch development

2004-10-04 Thread Arnt Karlsen
On Mon, 4 Oct 2004 11:16:28 -0500, Jon wrote in message [EMAIL PROTECTED]: ..meanwhile, is there a go-away flag that can be set to prevent us mortals and not from cvs co'ing known bad code trees? No because this repository is located at Sourceforge and there is no way to shutdown the

Re: [Flightgear-devel] CVS and branch development

2004-10-04 Thread Erik Hofman
Arnt Karlsen wrote: ..but the idea can be inverted: Maybe a cvs signature file to flag off stuff you're happy with? So I just set my script to check for that new flag file, and on its absense, just do cvs co to last Saturday night? In situations like that one is way too busy fixing stuff to

Re: [Flightgear-devel] CVS and branch development

2004-10-04 Thread Arnt Karlsen
On Mon, 04 Oct 2004 21:24:33 +0200, Erik wrote in message [EMAIL PROTECTED]: Arnt Karlsen wrote: ..but the idea can be inverted: Maybe a cvs signature file to flag off stuff you're happy with? So I just set my script to check for that new flag file, and on its absense, just do cvs co

Re: [Flightgear-devel] CVS and branch development

2004-10-03 Thread Mathias Fröhlich
Hi Jon, On Sonntag 03 Oktober 2004 16:06, Jon Berndt wrote: I am trying to save to JSBSim CVS some files I have modified for reading the new JSBSim XML format. These files should not be part of the main (HEAD) branch at the moment. I'm not sure I have done this correctly. Can a CVS expert

RE: [Flightgear-devel] CVS and branch development

2004-10-03 Thread Jon Berndt
Hi Jon, If I look at your last checkin, you already did that right. Just for the record: - Creating that new branch. - Checking out the new branch with cvs co -r BRANCHNAME - Work as usual within that newly checked out directory. Everything you do in that directory is done on that branch