[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Issue 524] Changed - line-ending conversion and keyword expansion

From: Kevin Pilch-Bisson <kevin_at_pilch-bisson.net>
Date: 2001-11-08 19:03:28 CET

On Thu, Nov 08, 2001 at 07:00:39PM +0100, Branko ?ibej wrote:
> >>+ Consider a shop that is primarily windows, but with a unix svn server.
> >>+ We would like to be able to specify that the default format for files
> >>+ in the repository is windows, so that clients don't have to spend the
> >>+ time doing translation all the time. Then files that HAVE to be dos
> >>+ would be marked dos, and files that HAVE to be unix would be unix etc.
> >>+
> >>+ This allows the client to be more efficient, by not always translating
> >>+ to the format of the server.
> >>+
> >>+ This allows lets any unix clients no that the repository files will
> >>+ be in dos format, and that THEY would have to do the conversion.
> >>+
> >>+ Clearer now?
> >>
>
> I guessed it would be something like that. However, that doesn't change
> my position: the native newline separator is a property of the whole
> repository. I really don't see why one should be able to change this per
> file, or per directory.
>
Another use case: Say you have a shop which maintains multiple products
some for windows some for unix. They may want to have the windows products
dirs default to windows line-endings, and the unix ones default to unix
line-endings.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson                    http://www.pilch-bisson.net
     "Historically speaking, the presences of wheels in Unix
     has never precluded their reinvention." - Larry Wall
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  • application/pgp-signature attachment: stored
Received on Sat Oct 21 14:36:48 2006

This is an archived mail posted to the Subversion Dev mailing list.