why is jk_registry.h in ./jk/native2/common? /2
Hi folks, can please some of the other commiters give some feedback? possible responses are: [ ] dont know [ ] move it to ./jk/native2/include [ ] dontr move it - it has to stay in common for xxx reason I'm for moving it - which raises the question if a file can be moved from one dir into another in CVS? Can a CVS guru please comment? just looking at ./jk/native2/common and asking me for whatever reason the jk_registry.h is in ./jk/native2/common and not in ./jk/native2/include ?? For that one .h I have to -Include the common dir... should we move it to ./jk/native2/include ? Guenter. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: why is jk_registry.h in ./jk/native2/common? /2
From: Günter Knauf [EMAIL PROTECTED] [X ] dont know If moving the file loses its CVS history it may be a good reason for it to stay put. -Kurt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: why is jk_registry.h in ./jk/native2/common? /2
Hi Guenter, I don't see any reason not to move it, but I would be sure to update the devstudio as well as build.xml files. Probably the best thing to do is delete it and commit it with a message indicating the original location. Keith -Original Message- From: Günter Knauf [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 15, 2004 8:54 AM To: [EMAIL PROTECTED] Subject: why is jk_registry.h in ./jk/native2/common? /2 Hi folks, can please some of the other commiters give some feedback? possible responses are: [ ] dont know [X] move it to ./jk/native2/include [ ] dontr move it - it has to stay in common for xxx reason - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: why is jk_registry.h in ./jk/native2/common? /2
On Tue, 15 Jun 2004, Kurt Miller wrote: | From: Günter Knauf [EMAIL PROTECTED] | [X ] dont know | | If moving the file loses its CVS history it may be a good reason | for it to stay put. Ehh - no, that's a really bad reason. It will get a new history -from there on-, but it will still have its old history from where you moved it from. So that if you check out the 14th of June 2004 version, it will be in its old place, and everything will compile, and if you check out the 15th of June 2004 version, it will be in its new place (and not its old), and everything will compile. Get it? Endre. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
why is jk_registry.h in ./jk/native2/common?
Hi, just looking at ./jk/native2/common and asking me for whatever reason the jk_registry.h is in ./jk/native2/common and not in ./jk/native2/include ?? For that one .h I have to -Include the common dir... should we move it to ./jk/native2/include ? Guenter. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
