+1 to 'svnsync info' (the concept, not the specific patch, which I haven't
As for a break-lock command, I think we'd be better served by a flag to the
'sync' and 'copy-revprops' commands (--force-lock) than a whole new subcommand.
David Glasser wrote:
> I'm pretty sure at some point we decided it would be a good idea to add
> some sort of svnsync break-lock command, even.
> On Jan 3, 2009 7:25 AM, "Ben Collins-Sussman" <sussman_at_red-bean.com
> <mailto:sussman_at_red-bean.com>> wrote:
> To play devil's advocate, why is 'svn proplist -v --revprop -r0 URL'
> more convenient than 'svnsync info URL'? Just fewer flags to type?
> I have two worries about this:
> * Historically, we've tried to keep the number of subcommands small.
> It takes a *really* strong argument to add a new subcommand.
> * This begins a precedent of 'hiding the implementation details' of
> svnsync, and I'm not sure we want that. It's never been our goal to
> hide the fact that svnsync tracks work via r0 revprops. In fact, I'd
> argue that we *want* users to know how svnsync works, so that they can
> modify revprops when necessary (e.g. fixing a stuck sync by removing
> an orphaned svn:sync-lock property.)
> On Fri, Jan 2, 2009 at 3:17 AM, Chris Foote <cafoote_at_yahoo.com
> <mailto:cafoote_at_yahoo.com>> wrote: > The following patch adds...
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2009-01-05 16:51:52 CET