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

Re: Newlines, preserving data, and multiple access paths

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2001-12-14 19:49:52 CET

This is a real issue, but we have enough to do already. Let's please
put this kind of thing off till post-1.0.

That'll be a wonderful day, the day we have problems because so many
non-Subversion tools are accessing Subversion repositories. That day
is not today. :-)

-K

Mark Benedetto King <bking@answerfriend.com> writes:
> > 2. Unfortunately, as I noted in one of my many other messages today,
> > *none* of the schemes presented so far will robustly handle tools
> > which access the repository through DAV or libsvn_fs, if the tools
> > run on varying platforms and aren't forgiving about newlines. In
> > order to do that, we have to actually add the concept of a text
> > file to the FS layer.
> >
>
> I proposed a solution on IRC to handle this case. It seems to me that
> what we want here is something like a "view", i.e., a WC-specific set
> of properties. What if we embed the WC-desired CR/NL/CRNL semantics
> *in* the request URL?
>
> http://svn.collab.net/CR/repos/svn/trunk
> http://svn.collab.net/NL/repos/svn/trunk
> http://svn.collab.net/CRNL/repos/svn/trunk
>
> And then let an apache module sort out the rewriting?
>
> Alternatively, we could do:
>
> http://svn.collab.net/repos/svn/trunk?record=CR
> http://svn.collab.net/repos/svn/trunk?record=NL
> http://svn.collab.net/repos/svn/trunk?record=CRNL
>
> And let mod_dav sort out the rewriting. I'm not sure
> if all DAV tools can include a query-string, though.
>
> Another alternative would be to use an SVN branch that
> had alternate default properties:
>
> http://svn.collab.net/repos/CR/svn/trunk
> http://svn.collab.net/repos/NL/svn/trunk
> http://svn.collab.net/repos/CRNL/svn/trunk
>
> This would require server-side implementation of the
> separator semantics (which goes against the current
> proposals, but does clean up this mess). Also, these
> branches would probably need to be read-only.
>
>
> Comments?
>
> --ben
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:53 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.