On 3/15/07, Karl Fogel <kfogel@red-bean.com> wrote:
> "C. Michael Pilato" <cmpilato@collab.net> writes:
> > I used to be in favor of this, but now I'm not so sure. The idea of a shell
> > mode for 'svn' that seems most intuitive to me is simply an interactive way
> > to do all the other things that 'svn' can do today with multiple subcommand
> > invocations. But MUCC is strictly about doing a single particular task that
> > you *can't* do with a string of 'svn' subcommands today. A shell mode for
> > 'svn' probably needs to be a little more full-featured, able to examine
> > working copies and repositories alike -- MUCC's use-case doesn't care about
> > working copies. Also, I need MUCC to maintain a non-interactive mode.
> >
> > If all these things can be satisfied by introducing 'svn shell', that's cool
> > -- I don't think I'd fight it. But I guess I'm thinking "baby steps" here.
> > contrib/client-side/mucc.c --> subversion/svn-mucc/main.c is a
> > super-trivial change. And in anticipation of this move, I even recently
> > rewrote the mucc test script to sorta-kinda use our Python test framework.
> >
> > If folks are cool with introducing svn-mucc, I'm volunteering for the task.
>
> The point of a shell mode is that it all happens in one txn (which is
> exactly the point of mucc, AIUI). You do a bunch of things, and then
> you "commit". Any shell mode is also a non-interactive scripting mode
> too -- just feed the commands on the shell's stdin.
>
> Given this new understanding of the proposed svn shell mode, do you
> still prefer mucc?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
A shell would be so nice! I used mucc just today (and was happy it
was available). But I had to build up the commands in a seperate file
and then join all the line to call them with the mucc command. It was
awesome to be able to do all the copys/moves in one commit (since they
were all related), but an interactive version would be great.
Also, it would cut down on this kind of session (depending on the
implementation):
svn ls svn://hostname/repo
svn ls svn://hostname/repo/branches
svn ls svn://hostname/repo/branches/testbranch
Just to look around at the repo structure.
troy
--
"Beware of spyware. If you can, use the Firefox browser." - USA Today
Download now at http://getfirefox.com
Registered Linux User #354814 ( http://counter.li.org/)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Mar 17 05:14:58 2007