On Wed, Jul 04, 2007 at 06:55:13PM +0200, Charles Acknin wrote:
> On 7/4/07, mark benedetto king <mbk@lowlatency.com> wrote:
> > # svn mv path/to/file path/to/newfile
> >
> > The above syntax looks pretty good to me. It's tweakable, reviewable,
> > and extremely well documented. Also, it's tolerant of revision skew
> > between WCs.
> >
> > Finally, people with older clients can pipe it through "cut -c2- | bash".
> >
> > Is there a drawback to this approach that I'm missing?
>
> Off the top of my head, I can see two:
> - you cannot deal with binary changes this way
> - it's svn-centric: 'svn' is the client that comes with subversion,
> there's no reason someone using another client - GUI or not - be faced
> with svn specific commands.
>
> (BTW, I'm using 'svn' client exclusively :-)
>
> Cheers,
> Charles
Okay, so instead:
# mv path/to/file path/to/newfile
No more svn-centricity (and less space, to boot).
I think it would be fine to encode binary deltas exactly as you have
proposed; those are inherently "computer-only".
--ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 4 23:57:33 2007