RE: [Flightgear-devel] CVS and branch development
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 PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] CVS and branch development
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 inform me what the correct procedure is to tag a subset of files with a branch tag, store them in CVS, and then commit changes as they are made? Also, I would need to know how to merge or commit changes from the branch to the main HEAD line upon completion of development. If I look at your last checkin, you already did that right. Something did not work correctly. All my commits went to the HEAD branch. Crap! I've got some stuff to undo, now. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS and branch development
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 working on it by doing : cvs update -r JSB_New_XML FGAircraft.cpp FGAircraft.h check with : cvs status FGAircraft.cpp FGAircraft.h you should see JSB_New_XML as a sticky tag. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] CVS and branch development
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 it by doing : cvs update -r JSB_New_XML FGAircraft.cpp FGAircraft.h check with : cvs status FGAircraft.cpp FGAircraft.h you should see JSB_New_XML as a sticky tag. -Fred Is there a good way to revert the HEAD branch of CVS to yesterday morning's set of files? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS and branch development
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 working on it by doing : cvs update -r JSB_New_XML FGAircraft.cpp FGAircraft.h check with : cvs status FGAircraft.cpp FGAircraft.h you should see JSB_New_XML as a sticky tag. -Fred Is there a good way to revert the HEAD branch of CVS to yesterday morning's set of files? If I recall correctly, cvs admin -orev filename will kill the so called rev revision. For example, cvs admin -o1.42 foo.cxx remove revision 1.42 of foo.cxx. But look at the cvs manual before proceeding -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS and branch development
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 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 FGAircraft.h check with : cvs status FGAircraft.cpp FGAircraft.h you should see JSB_New_XML as a sticky tag. -Fred Is there a good way to revert the HEAD branch of CVS to yesterday morning's set of files? If I recall correctly, cvs admin -orev filename will kill the so calledrev revision. For example, cvs admin -o1.42 foo.cxx remove revision 1.42 of foo.cxx. But look at the cvs manual before proceeding ..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? -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS and branch development
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 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 FGAircraft.h check with : cvs status FGAircraft.cpp FGAircraft.h you should see JSB_New_XML as a sticky tag. -Fred Is there a good way to revert the HEAD branch of CVS to yesterday morning's set of files? If I recall correctly, cvs admin -orev filename will kill the so calledrev revision. For example, cvs admin -o1.42 foo.cxx remove revision 1.42 of foo.cxx. But look at the cvs manual before proceeding ..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 ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] CVS and branch development
..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 fixed today. In teh meantime, checkout JSBSim CVS only based on data, from say, last Saturday night. That should be fine. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] ATC Network Test
A few details... Volunteers will get a package of software that contains the TNL libraries and a basic set of software to connect to the ATC net as a controller or pilot. Package will include ALL source code and make files for a Linux system. Sorry, I'm just not an MS type. However, it will build under Cygwin. Building will create two application programs --- controller and pilot During the time window for the test you can login to the master as a pilot or controller as in controller IP_address_TBS:port or pilot IP_address_TBS:port Both values to be provided at the time of the test... As a controller node, initially login will be ack'ed by the master and the node added to the master list. Loggin in as a pilot node (assuming a controller node is present) will receive a list of controller nodes from the master, at which point a controller node is selected from the list and a request is made to the master to arramge a connection with the selected controller. (NOTE: Current selection is random, scope criteria are TBS). Once the connection is accepted the controller and pilot exchange a string of secret data. After about 30-40 secs the connection will be broken by either node and a reconnect may or may not be attempted (Again a random event at this time to keep things somewhat dynamic and unpredictable) Test objectives are simple: 1) test network loading on the server 2) determine latencies issues 3) test robustness of master server and protocol for error recovery 4) identify/motivate interested participents as future developers and/or players 5) create a forum for ideas For example, it would be possible using FG with a view position from the tower to connect several flights from friends and observe their performance while doing circuits and act as the tower controller... Of course, that idea needs a bit more thought and probably a lot more development, but it is doable. Regards John W. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS and branch development
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 repository during this maintenance operation. -Fred I'll try and get this fixed today. In teh meantime, checkout JSBSim CVS only based on data, from say, last Saturday night. That should be fine. ..ok. I'm asking because I'm pondering an automatic build script that I'd like to abort in situations like this, when cvs co, building etc is pointless. ..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? -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS and branch development
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 bother about others. Sorry about that. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS and branch development
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 to last Saturday night? In situations like that one is way too busy fixing stuff to bother about others. Sorry about that. ..I said on its absense, the idea is you fix stuff first, then set the new Ok, I'm happy flag. ..but true, another way could be chk whether or not any of you guys are working on the cvs server to fix stuff like this. ..it has to be automated anyway. Checking the history section in the manual. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] ATC Network Test
On Mon, 04 Oct 2004 11:17:07 -0700, John wrote in message [EMAIL PROTECTED]: A few details... Volunteers will get a package of software that contains the TNL libraries and a basic set of software to connect to the ATC net as a controller or pilot. Package will include ALL source code and make files for a Linux system. Sorry, I'm just not an MS type. However, it will build under Cygwin. ..GPL? Url? Building will create two application programs --- controller and pilot During the time window for the test you can login to the master as a pilot or controller as in controller IP_address_TBS:port or pilot IP_address_TBS:port Both values to be provided at the time of the test... As a controller node, initially login will be ack'ed by the master and the node added to the master list. Loggin in as a pilot node (assuming a controller node is present) will receive a list of controller nodes from the master, at which point a controller node is selected from the list and a request is made to the master to arramge a connection with the selected controller. (NOTE: Current selection is random, scope criteria are TBS). Once the connection is accepted the controller and pilot exchange a string of secret data. After about 30-40 secs the connection will be broken by either node and a reconnect may or may not be attempted (Again a random event at this time to keep things somewhat dynamic and unpredictable) Test objectives are simple: 1) test network loading on the server 2) determine latencies issues 3) test robustness of master server and protocol for error recovery 4) identify/motivate interested participents as future developers and/or players 5) create a forum for ideas For example, it would be possible using FG with a view position from the tower to connect several flights from friends and observe their performance while doing circuits and act as the tower controller... Of course, that idea needs a bit more thought and probably a lot more development, but it is doable. Regards John W. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] ATC Network Test
Arnt Karlsen wrote: On Mon, 04 Oct 2004 11:17:07 -0700, John wrote in message [EMAIL PROTECTED]: A few details... Volunteers will get a package of software that contains the TNL libraries and a basic set of software to connect to the ATC net as a controller or pilot. Package will include ALL source code and make files for a Linux system. Sorry, I'm just not an MS type. However, it will build under Cygwin. ..GPL? Url? John isn't yet 'releasing' anything, rather he asks for people who would be willing to participate in some field tests. John: I haven't yet had the time to get back to your other eMails, but concerning what you mentioned above, I would suggest to have me look into your makefiles or sources where necessary, so that we can adapt them accordingly - if I am not wrong, you shouldn't have made much use of anything unix/linux-specific so far, so at this stage of the process, it's certainly pretty straight-forward to make the configure/makefile scripts support windows/mac, too. Particularly because of opentnl's cross-platform nature. - Boris P.S.: I don't think it's necessary for me to mention that I would be glad 'to volunteer' :-) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] ATC Network Test
- Original Message - From: Boris Koenig [EMAIL PROTECTED] To: FlightGear developers discussions [EMAIL PROTECTED] Sent: Monday, October 04, 2004 1:46 PM Subject: Re: [Flightgear-devel] ATC Network Test Arnt Karlsen wrote: On Mon, 04 Oct 2004 11:17:07 -0700, John wrote in message [EMAIL PROTECTED]: A few details... Volunteers will get a package of software that contains the TNL libraries and a basic set of software to connect to the ATC net as a controller or pilot. Package will include ALL source code and make files for a Linux system. Sorry, I'm just not an MS type. However, it will build under Cygwin. ..GPL? Url? it's GPL. I still have a little work to do to create a clean build and install as well as reducing the size by including only the essential library files. TNL did a great job of creating docs and sample programs, but they tend to bloat the package and create unnecessary build issues. John isn't yet 'releasing' anything, rather he asks for people who would be willing to participate in some field tests. Boris is correct, not so much a release as a head count, but I'll probably upload it to the ftp server at kingmont or I might just set up a machine locally that I plan to also use as the master Regards John W. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
