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

Re: Proposed feature: safer alternative to svnput

From: Philip Martin <philip_at_codematters.co.uk>
Date: Sat, 06 Sep 2008 14:45:57 +0100

Karl Fogel <kfogel_at_red-bean.com> writes:

> Markus Kuhn <Markus.Kuhn_at_cl.cam.ac.uk> writes:
>> Can it read SRC-FILE from stdin?
>
> No, I don't think it can.
>

As of today (r32940) one can use

  $ svnmucc -- put - URL

to read from stdin.
 
> I'd love to see the svnmucc functionality subsumed into the 'svn'
> client. Note that there's been talk of writing a "shell" mode for
> 'svn'. It would achieve svnmucc's multi-operation feature something
> like this:
>
> svn shell
> > open http://my.repos.com/trunk/
> > mv README README.txt
> > rm README.MSDOS
> > mkdir build
> > [...]
> > commit
>
> ...where "commit" means the same thing it does in a db client :-).
> (You could imagine other commands to cat in or out of a file, too.)

Karl is probably already aware of this but I'll add that "svn shell"
is more complicated than simply mapping the various mv/rm/mkdir
commands to corresponding editor calls. The reason is that the commit
editor must traverse the directory hierarchy once only but the person
entering the commands will not want to woory about that. So user
commands like:

  open
  mv foo/X bar/X
  mv bar/Y foo/Y
  commit

must get translated into editor calls such as:

  open
  delete foo/X
  copy to foo/Y from bar/Y_at_base
  delete bar/Y
  copy to bar/X from foo/X_at_base
  commit

which can only be done once all the commands are known.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-06 15:46:38 CEST

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