I am trying to setup our Unix-based CVS repository to run dos2unix when
files are committed, but I'm not having much luck and don't see any solution
laid out clearly in the mailing lists.
I have a commitinfo file...
DEFAULT dos2unix
When I commit my Windows text file...
~/webapps cvs ci -m
On Fri, 13 Jun 2003, Andy Kriger wrote:
I am trying to setup our Unix-based CVS repository to run dos2unix when
files are committed, but I'm not having much luck and don't see any solution
laid out clearly in the mailing lists.
CVS in client-server mode already performs the conversions.
(You
At 11:47 AM 6/13/2003, Andy Kriger wrote:
I am trying to setup our Unix-based CVS repository to run dos2unix when
files are committed, but I'm not having much luck and don't see any solution
laid out clearly in the mailing lists.
Don't attempt to use a commitinfo script to change a file being
: Frederic Brehm [mailto:[EMAIL PROTECTED]
Sent: Friday, June 13, 2003 13:38
To: Andy Kriger; [EMAIL PROTECTED]
Subject: Re: Using dos2unix on commit???
At 11:47 AM 6/13/2003, Andy Kriger wrote:
I am trying to setup our Unix-based CVS repository to run dos2unix when
files are committed, but I'm not having
At 03:25 PM 6/13/2003, Andy Kriger wrote:
As background, what is prompting this need is multiple developers with
different IDEs making connections to CVS. Since there's no way to be sure
what line format is being used, I'm looking for consistency.
Good luck.
The way to decrease the chances of
Andy Kriger writes:
As background, what is prompting this need is multiple developers with
different IDEs making connections to CVS. Since there's no way to be sure
what line format is being used, I'm looking for consistency.
You've got hold of the wrong end of the stick. It is the
Ok sorry for the screwed up emails I have been sending around, I might
have this one addressed correctly :-)
Most of the info here has already been mentioned, a small part that
we experienced has been left out. The cygwin cvs client does not
fix up the line endings on the commit. At least the
mike walster writes:
The cygwin envinronments
are installed with unix style the default for that system.
That is the root of your problem. You should *NEVER* install cygwin
with Unix line endings -- if you want a Unix-like system, you know where
to find it. Having some of your tools use one
On Fri, Jun 13, 2003 at 06:01:18PM -0400, Larry Jones wrote:
What do you mean by [line-ending problems] causing merges to panick? I can see
causing the
developer to panic since the entire file will be completely different
from CVS's perspective, but CVS shouldn't have a problem with it.
I
One must be carefull about the words one chooses here
I did indeed use the term panick spelled with a ck loosley.
The files do show up completely different which was causing
the developer to panick somewhat.
As I recall the instructions for cygwin say to always install
as unix line endings. I
10 matches
Mail list logo
