Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
I develop on a windows box, but keep my files on a samba drive. The host machine for this network drive also has our compiling tools, which are linux-based. By and large, I work with files telneted in using the command-line tools, but for a large or complex operations, I prefer to rely on what I know in the windows environment. In particular, I use TortoiseCVS for diffs, histories, and conflict merges. Long story short, the removal of the --lf option from cvsnt means I can no longer work directly on my samba drive any more. A previous post on this list suggests that is is to ensure that the client cannot send LFs to poison the repository, and I see how that would work for local drives. It doesn't work at all for networked drives, though, as it removes the only option I had for keeping the repository clean. That same post I found suggests using the -k+L option on checkout as a safer method than --lf. cvsnt doesn't recognize this kopt, however. Could someone please offer me a solution for maintaining this shared sandbox? I realize that --lf is a sharp knife, but a knife is a useful tool, and I'm careful with my tools. I do find it a bit ironic that the removal of the --lf, in the name of safety, created a situation that, was I paying less attention, certainly would have dirtied my repository. Thanks, Jason