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

Re: [PATCH]: Transform rules prototype

From: Daniel Berlin <dberlin_at_dberlin.org>
Date: 2005-11-06 17:37:19 CET

On Sun, 2005-11-06 at 10:50 +0200, Alan Barrett wrote:
> On Sat, 05 Nov 2005, Daniel Berlin wrote:
> > This patch implements a prototype version of transform rules to save
> > typing.
>
> > The command line
> > svn ls rule://release#4_0/gcc/ChangeLog
> >
> > will become:
> > svn ls svn://gcc.gnu.org/svn/gcc/branches/gcc-4_0-branch/gcc/ChangeLog
>
> This still doesn't handle deeply nested directories conveniently.
>
> For example, if you are working in a deeply nested subdirectory of the
> working copy, and you want to diff a file against the corresponding file
> in the corresponding deeply nested subdirectory of another branch, you
> still need to say something like this:
>
> svn diff rule://release#4_0/gcc/fixinc/tests/base/arch/i960/archI960.h \
> archI960.h
>
> where Greg's proposal would allow something like this:
>
> svn diff -r release#4_0 archI960.h

Yes, but his proposal has it's own set of issues, such as requiring
dir-props (which means read-only users can't set them), and the
disadvantage that now every single command will have to play around in
the wc to try to find transform rules, which IMHO, is a very bad idea.

I'm not opposed to a -t or -r style syntax that appends the current path
in the repo to the end of the command.

But we also can't make this scheme so complex that nobody actually
understands how to work with it.

>
>
> Also, if you invent your own URI scheme,

I'm sorry you wrote the rest of that detailed explanation. I thought i
made it clear that I only made it rule:// to make it easy to play with.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 6 17:38:14 2005

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.