Re: How should 'svn log' behave with peg revisions?

[Julian Foad <ju...@btopenworld.com>]

kfogel@collab.net wrote:
> Please see S. Ramaswamy's post and patch here:
> 
>    http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=101980
> 
> He's fixing issue #2287, by making 'svn log' able to take peg
> revisions, e.g.:
> 
>    $ svn log -rN url_that_does_not_exist_in_head@X

[...]
> We've already fixed other commands, such as 'svn cat', to not treat -r
> operands this way, and to use '@N' peg rev syntax instead.  We just
> hadn't gotten around to fixing 'svn log' yet -- that's what issue
> #2287 is about.
> 
> If we make this change, 'svn log' will be consistent with other
> commands.  But, the behavior change will be unusually user-visible.
> We could just say:
> 
>    "The old behavior was a bug, get used to the nice, shiny new
>     consistency of everyone taking peg revs."
> 
> In fact, Ben Collins-Sussman and I think that's fine.  But, it's
> drastic enough that we thought we should ask here first.
> 
> Thoughts?

+1 on doing this.  But, as somebody noted somewhere, Ben Reser made the point 
very strongly last year that if this user interface has to change, the change 
should at least be clearly documented in the release notes and the book.

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org