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

Re: test editor

From: Karl Fogel <kfogel_at_collab.net>
Date: 2001-05-15 20:44:50 CEST

Ben Collins-Sussman <sussman@collab.net> writes:
> Actually, Mike -- that test-editor, when attached to commits, is
> *really* useful. I'm sure I will want it again sometime soon. I just
> talked to Karl, and we agree that it should be a runtime switch.
> svn ci -t
> or something. In other words, maybe you can take 10 minutes to make
> this so? Keep on linking the commandline against the test library
> forever; just make the editor composition an optional runtime thing.
> What do you think?

To clarify: we should do what CVS does, where -n and -t are
independent but can be used together. Here's the relevant quote from
CVS's help:

   fermat$ cvs --help-options
       -n Do not execute anything that will change the disk.
       -t Show trace of program execution -- try with -n.


   svn --trace /* Adds the trace editor to the composition. */
   svn --do-nothing /* Subtracts the actual commit editor */
   svn --trace --do-nothing /* Thus, svn shows what it would have
                                 done, but doesn't actually do anything. */

But, let's not make this change now. Let's just revert back to using
the commit editor, so we can tag M2 today, then make the above change
as part of development toward M3. :-)


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:30 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.