Re: How to keep unix eoln in repository

[juhas]

On Tue, 14 May 2002, Shubhabrata Sengupta wrote:

> Why would you need to change it to unix eolns - if you are developing on
> windows and using cvs on windows to check the files in.

Since win eolns are annoying ;-)
In addition win eolns can confuse some tools I depend on.
Well, I know that to develop tools which are platform dependent is
not very handy, but there is nothing I can change about it...
Wish I was a manager... ;-)

> It is up to the
> cvs client to translate from/to the correct eoln. Files are always
> stored with unix eolns on the CVS server.

Rubbish..
Maybe in your sweet bug-free world...
When I see win eolns in $CVSROOT/files.c,v it mihgt be buggy cvs version:
cvs -v
Concurrent Versions System (CVS) 1.11 (client/server)
or bad cvs administrator (I inhereted the repository as is)
or bad client
or st. else
Nevertheless, to keep the repository as clean as possible is a part
of my job now.

>
> Shubho
>
> juhas wrote:
>
> >Hi,
> >is there any simple way how to keep unix ends of lines (eolns) in
> >the repository?
> >Despite the fact that our compile & link platform is UNIX, some
> >of our developers edit source files on windows. And they always
> >forget to change win eolns to unix eolns...
> >Is it possible to set/write a trigger which would convert eolns
> >in text files during cvs checkin?
> >If not, is there another chance?
> >Thanks a lot,
> >Dusan Juhas
> >
> >
> >_______________________________________________
> >Info-cvs mailing list
> >address@hidden
> >http://mail.gnu.org/mailman/listinfo/info-cvs
> >
> >
>
>

-- 
Dusan Juhas