Okay, phew. The CVS server is synchronized again. Please
start using it again.
I'd suggest you discard your old CVS snapshot, rather
than try to "update" it. The "EF.rc" file got set with a sticky
tag, so it will not correctly update to 1.12, but will stay at
1.6 (which breaks things).
Please Reply via email and confirm you have the new
Code snapshot and are working from that going forward. Thanks!
-Scott
On Wed, 13 Mar 2002, Scott C. Best wrote:
> Kaboodle-developers:
>
> There are now 5 independent teams working on Kaboodle
> development. So it is very important that we identify how we're
> going to use the CVS repository without destroying other people's
> work.
> Here is what I suggest:
>
> 1. Use WinCVS to create for yourself a snapshot of the code
> that's sitting in the CVS server. Put this data into a safe
> folder, but *do not edit it*.
>
> 2. Copy that "snapshot folder" to a "working folder". Do all of
> your edits in that working folder.
>
> 3. Everyday, startup WinCVS and do a "Query -> Query Update" on
> your snapshot folder. It will tell you what files in your
> snapshot folder need to be updated.
>
> 4. If something in your snapshot folder needs to be updated,
> run Update on your snapshot folder, and copy *just the files
> that are new* to your "working folder". Then verify that all
> of your edits still compile without error. Again, *do not
> make edits* in the "snapshot folder".
>
> 5. After you've run this Update, and things compile without error,
> copy *your* files from your working folder to your snapshot folder,
> and then Commit that snapshot folder to the CVS server. You should
> *never* commit changes to the CVS server without first Update'ing
> and verifying that any new pieces work with your changes.
>
>
> Finally, CVS tries to deal with End-Of-Line characters
> automatically. The CVS server is running on a Linux machine, though
> the programming is being done on Windows machines. This means that
> every time you transfer files from the CVS server to your Windows
> machine, the <LF> in the file is converted to <CR><LF>. Similarly,
> when you send files from a Windows machine to the server, the
> <CR><LF> in the Windows files are converted to just <LF>.
>
> There's a problem with CVS in that it doesn't do this
> very reliably when moving data from PC to server. So, occasionally,
> the file will get into the CVS server with <CR><LF>. The next time
> you download the file, CVS will translate that into <CR><CR><LF>,
> which Visual Studio will complain about. It will turn that into
> <CR><LF><CR><LF> which makes your whole file double-spaced.
>
> If you every notice this, please let me know. I can run a
> CVS client on the CVS server, and cleanup these broken EOL characters.
> I've not been able to discover exactly what causes these errors to
> sneak into the server.
>
> Please let me know if I can clarify anything. Thanks!
>
> -Scott
>
>
>
> _______________________________________________
> Kaboodle-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
>
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
