-----BEGIN PGP SIGNED MESSAGE-----
To play devil's advocate to your devil's advocate (would that be an angel's
advocate?): why implement something like changelists? Why not just edit a file
and use '--targets'? What about merge tracking? Fact is we've not made many
secrets about how the internals of Subversion work, but we've (often) gone to
great lengths to simplify its usage for our users.
All that being said, I understand the desire to not add more options to svnsync,
but in this case, I feel it's warranted.
Ben Collins-Sussman 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> wrote:
>> The following patch adds an 'info' subcommand to svnsync that prints out the
>> syncronisation information of a repo. This is more convient than using an
>> svn proplist command.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Received on 2009-01-04 04:48:45 CET