[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 21:55:57 CET

On Sun, 2005-11-06 at 21:49 +0100, Branko Èibej wrote:
> Daniel Berlin wrote:
> > Anyway, i'm just going to implement prepending transform rules for now,
> > and a -t syntax, and remove the current rule://
> >
> Pleas don't hurry so. I know the GCC people want this, but we can't
> release a change like this before 1.4, and there's not been even
> remotely enough discussion on the list.

Again, i'm just playing around with various options.

I have *serious* doubts we are going to be design a good UI by simply
talking about it here.
In fact, i'd -1 any discussions of this feature that have no real
implementations behind them to try.

I believe that's one of the ways we got into this problem of
ridiculously long command lines in the first plcae.
>
> Please let's do things the right way. Start with a design doc stating
> the goal of the change, defining the syntax formally, exploring effects
> on current commands, etc. etc. etc. Then we'll discuss this design on
> the list. *Then* we'll implement it.

Again, i believe it's way too early for a design doc. You need to have
some idea of what kind of ui you actually want before you can work up a
design doc.

How the heck are you supposed to decide what UI's work if you can't try
them in a real world situation?

>
> Even though I support this idea in general, it's so sweeping a change
> that it gets a -1 from me if it's implemented without all the necessary
> process that such a change requires.

That's fine.

>
> -- Brane
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 6 21:56:40 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.