You have exactly the same symptoms I had: not all, only some files exhibited this behavior. (Maybe these were the Mac-edited files? Just a wild guess...) However, everything got well after I: 1. did a fresh cvs login with --crlf (without this, other commands (diff, checkout) with --crlf will give you access denied. Weird but true.) 2. did a cvs checkout with --crlf
So yes, I guess you should use --crlf with all commands. I use it with login, checkout, and diff -- the only commands so far I use, since I'm not a committer :-) Attila. ----- Original Message ----- From: "Donnie Hale" <[EMAIL PROTECTED]> To: "Velocity Developers List" <[EMAIL PROTECTED]> Sent: 2002. janu�r 8. 3:23 Subject: RE: [ANN] Struts + Velocity + Tools +... > This is good info, as I am using a Windows CVS client (TortoiseCVS). > However, I don't see the problem on every file I've gotten from > velocity-tools, so there's definitely some difference in the files that are > in CVS even if how I'm retrieving them impacts how I see them. > > To make sure I understand, this option should be used for all cvs actions, > checkout included? > > Thanks, > > Donnie > > > > -----Original Message----- > > From: Attila Szegedi [mailto:[EMAIL PROTECTED]] > > Sent: Monday, January 07, 2002 7:00 AM > > To: Velocity Developers List > > Subject: Re: [ANN] Struts + Velocity + Tools +... > > > > > > CVS client on Windows messes you up. I had the very same issue when I > > submitted patches to Velocity. You should specify the --crlf option to the > > CVS. Note: you will need to re-login, and specify --crlf to cvs login as > > well, otherwise it won't work. > > > > Attila. > > > > ----- Original Message ----- > > From: "Gabriel Sidler" <[EMAIL PROTECTED]> > > To: "Velocity Developers List" <[EMAIL PROTECTED]> > > Sent: 2002. janu�r 5. 19:53 > > Subject: Re: [ANN] Struts + Velocity + Tools +... > > > > > > > Donnie Hale wrote: > > > > > > > > Gabe and Geir, > > > > > > > > I use Visual SlickEdit. When I open a file that has the > > problem, it has > > > > extra blank lines with one of those funny characters at the > > start of the > > > > next non-blank line. VS has no problem opening DOS or Unix files in a > > > > correct way automatically - I do it all the time (been using VS for 8 > > years, > > > > so I know it really well). When I see that problem, I look at the file > > in > > > > hex mode, and that's how I know that the lines end with > > "\x0D\x0D\x0A". > > > > Additionally, not every ASCII file in the velocity-tools > > distro has the > > > > problem. About 1/2 of them (maybe more than 1/2) are perfectly fine. I > > can > > > > open one and see the problem then open the next file in the same > > directory > > > > and it's OK. > > > > > > > > Don't know what to tell you, but I'm sure the lines end that way. I > > don't > > > > know UltraEdit, but I'm betting it tweaks the line terminators when it > > opens > > > > the file. ?? > > > > > > > > > > Yes, you are right. UltraEdit is tweaking them. Now I know how > > to look for > > the > > > problem but not yet how to avoid it. Must be the Geir's Mac that > > interferes... ;-) > > > > > > Gabe > > > > > > > > > -- > > > Gabriel Sidler > > > Software Engineer, Eivycom GmbH, Zurich, Switzerland > > > > > > -- > > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > >
smime.p7s
Description: application/pkcs7-signature
