Thanks for your help and suggestions Jim. Since I check out from cvs and do my builds with Ant. I found the quickest solution through Ant by using: <fixcrlf srcdir="scripts" includes="**/*.sh, **/*.s
Hang on a sec - your original message didn't mention anything about tar. Is this something you do already, or something you're going to add into the mix? Can your application server check the files o
Thanks for your thorough reply Spiro. I suspected that they were ending up with the correct file endings on each environment respectively and that the wincvs client was converting them. So it looks l
I'd like to know whether it is possible that CVS is working with MS files ( doc, xls ) ? And it 's not, with which application that i could do this...? CVS will cope with files in this format as long
Rez wrote: Hi all How do I remove cvs watches set by other users who are no longer with our company? Is there any way to do this? Thanks Rez Here's how I remove cvs watches from my repository (cvs 1.
Luigi De Pietri wrote, On 01/08/2009 05:43 AM: Hello, I have a list of files that came from unix repository's back up i have placed them under a windows repository, but when i try to check out files
Hello Tom, [...] I would do it (and I have done it) in the following way: 0. Make sure that all text files use LF lineending only, and make sure you are on a machine where LF is the natural line end
checking a file as-is should have been the default, and changing its line endings should have been a nice feature to enable. I disagree (as obviously have everyone who worked on the code before toda
Paul, If you check the file out on the platform for which the text is ultimately destined, you would not have this problem. Check it out on Windows, it works on Windows. Check it out on Linux, it wo
Quite the opposite, YOU told cvs (via -kb) not to change the file, and it obeyed, i.e., you added the file with -kb and then committed it from MS, and on MS the file contained "/bin/ bash^M", and be
Ittay, I disagree (as obviously have everyone who worked on the code before today). What you suggest is unworkable. Let me explain by way of example: on OS/400 an ASCII stream file with LF line endin
Todd Denniston wrote: Ittay Dror wrote, On 09/11/2008 01:39 PM: Todd Denniston wrote: Ittay Dror wrote, On 09/11/2008 12:14 PM: Larry Jones wrote: Ittay Dror writes: <SNIP> On windows, are you using
Quite the opposite, YOU told cvs (via -kb) not to change the file, and it obeyed, i.e., you added the file with -kb and then committed it from MS, and on MS the file contained "/bin/bash^M", and beca
Ittay Dror wrote, On 09/11/2008 01:39 PM: Todd Denniston wrote: Ittay Dror wrote, On 09/11/2008 12:14 PM: Larry Jones wrote: Ittay Dror writes: <SNIP> On windows, are you using cvs under cygwin or CV
Quite the opposite, YOU told cvs (via -kb) not to change the file, and it obeyed, i.e., you added the file with -kb and then committed it from MS, and on MS the file contained "/bin/bash^M", and beca
ok, but in this case i'm not editing the file, i'm just moving it around to create a product tree. someone else edited it and committed and the build just so happens to run on windows. Can you not j
ok, but in this case i'm not editing the file, i'm just moving it around to create a product tree. someone else edited it and committed and the build just so happens to run on windows. Can you not j
Ittay, Can you not just run the build on unix? Not true. Yes many applications 'know how to handle' unix line endings on windows - but many then insert windows line endings (change the whole file or
No, it isn't OK. CVS always does diffs, even on binary files, so that isn't a concern, but CVS won't automatically merge binary files and the line endings in the repository may be messed up such that
No, it isn't OK. CVS always does diffs, even on binary files, so that isn't a concern, but CVS won't automatically merge binary files and the line endings in the repository may be messed up such that
I removed the accounts/finance/Salary//Pramod/ folder from the repository and ran the same command again cvs -t checkout module-name U accounts/finance/Salary/Keihi/Pavan/PavanAgrawal_200205.xls -kb,
Danish Siddiqui wrote, On 08/10/2007 10:00 AM: Todd Denniston wrote: Danish Siddiqui wrote, On 08/10/2007 05:39 AM: Hi, Im using the WinCVS 1.2 client. When I try to checkout a certain module from a
Thanks a lot. Finally some log messages so that I can move a wee bit forward. Im pasting the log messages i received when i ran `cvs -t checkout certain_module` under WinCVS U accounts/finance/Salary
Danish Siddiqui wrote, On 08/10/2007 05:39 AM: Hi, Im using the WinCVS 1.2 client. When I try to checkout a certain module from a repository, I get the **cvs exited normally with code 1**. The cvs se
That took care of it. Thank you. I don't like it when the lead CVS guru is out... -Ryan Sort of. First of all, note that -kb does *not* cause each version to be stored separately in the repository --
Sort of. First of all, note that -kb does *not* cause each version to be stored separately in the repository -- CVS still saves diffs. What -kb does do, however, is disable lineending conversions. S
Hello, This is not fully correct. CVS on Cygwin creates the line endings configured when you installed Cygwin. If you installed Cygwin to use Unix line endings, CVS on Cygwin uses Unix line endings.
It says "permission denied". But if i do the import of only files concerned (one by one), it's ok !! Any idea ? :-( It sounds like you have some kind of transient permission problem. Is your reposit
On further reflection, I realized that this is probably the source of your problems. Most likely, when they email or download the files, the files contain the line-ending convention of the person who
Find out. Putty and SSH are not CVS clients, but connection methods. The line-ending problem is very old, and has been solved many times without resorting to altering the file while it's on its way i
This is not the correct forum to ask questions about Tortoise or WinCVS or CVSNT. Tortoise and WinCVS both include the CVSNT client. To checkout with unix lineending simply use "cvs co -kL modulenam
HeyYou! wrote: Newbie: Can CVS or Tortoise or WinCVS be changing files originally saved in Unix line end format to PC line end format? If yes, what can I do to prevent this change? Yes. The CVS clien
Probably because network-mounted working drives are notorious for corrupting your work. In particular, line-ending conventions can cause problems. If you are sure the network drive is hosted on the s
The Windows client doesn't support SSH, does it? Which version are you using for the Windows client ('cvs version'). That is correct. However, sometimes the concept of "the client" gets a little blur
I think you want to run "cvs update -r int_branch" after creating the branch. Note the "-r" to specify the tag. Without the -r you are telling CVS to look for a module named int_branch instead of the
CVS Issues We have started to put a new CVS process in place but we are running into a few problems. We were trying to create a structure where we have an integration branch off the main branch and t
Hello, Why is this pointless? Did you ever try to have a project with MSVC .DSP and .DSW files opened if these files only have LF as line endings? MSVC refuses even to load these files. Russ also tol
Just thought I'd jump in again. CVSNT (Linux/Unix/Windows/Mac) already versions keyword expansions, and already has -kd and -ku (dos line endings and unix line endings) in addition to all the Unicode
Christian Hujer wrote: I do not see any course where lineending conversion is correct course of action. I'd even expect a CR/LF file checked in on Windows to retain it's CR/LF endings when checked i
Note: Microsoft compilers accept them for the most part. However, when dealing with dll exports the .def file _is_ sensitive to cr/lf-lf. We had an (very hard to debug) issue where our build failed b
Hi, Am Montag, 12. September 2005 07:00 schrieb Larry Jones: Okay, but I think talking of EBCDIC or other non-ASCII-based charsets / encodings is really pointless. Well, I don't know that many compil
Hi, Am Sonntag, 11. September 2005 23:27 schrieb Pierre Asselin: Your idea of decoupling keyword expansion, text/binary mode, mergability and line-ending conversion indepently of each other is really
Hi, Am Montag, 12. September 2005 05:57 schrieb Jim Hyslop: Good point. Yet there's some difference. 0x0A and 0x0D are in wide use, while 0x7f isn't (especially not in the sense of lineending). I do
Well, how does RCS react to an unrecognized keyword string? With a warning, an error, or silence, and what sort of substitution occurs? Regardless, the new modes could be stored in a newphrases (see
Yes, it would. Aye, there's the rub. If anyone has any good ideas (and, preferably, code) to do the former without the latter, please share! -Larry Jones I've got an idea for a sit-com called "Father
Then they're not text files. ISO 8859-1 files won't look anything like text on an IBM mainframe that uses EBCDIC instead of ASCII. Remember that the main motivation for CVS was source code control. C
Christian Hujer wrote: This is not the point of the program but of the file specification. If a file specification says "This is a text file. Line endings always have to be LF, regardless of the oper
Example: Data files from the Daimonin project (an MMORPG). They are ISO-8859-1 text files. They must explicitely only use LF for lineending. They won't work with CR/LF. The file format is specified
I believe Cygwin lets you mount directory hierarchies in "binary" or "text" mode. I forget the terminology and the exact details. One of the two behaves like Unix, the other like Windows. Whether CVS
Hi, Am Sonntag, 11. September 2005 16:28 schrieb Larry Jones: I definitely disagree here. Example: Data files from the Daimonin project (an MMORPG). They are ISO-8859-1 text files. They must explicit