Hello guys, (hi Erik ;-) )
Erik has just sent the mail I'm forwarding on subversion-dev [1], and it
immediately struck me as being a good idea, as we're having exactly the
same kind of "conceptual" mismatch between changeset and revision in
Trac's Subversion subsystem, when dealing with rX:Y or [X:Y] TracLinks.
I'd like to hear what you're thinking about this. If you also think it's
a good idea, we could voice our support on subversion-dev to help make
this happen. Having support for the 'cX-Y' syntax for changeset ranges
both on the svn command line and in Trac would be truly excellent!
Unfortunately, this won't make the problem go away completely, as there
would still be some ambiguity left in diff: and log: links. Maybe we
should also add the possibility to write those links as either log:rX:rY
or log:cX:cY, depending if we're talking about state at revision X (rX)
or changeset X (cX). X would still stand for rX, as it is now.
-- Christian
[1] - http://svn.haxx.se/dev/archive-2007-09/0532.shtml
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
--- Begin Message ---
Merge tracking has started using revisions differently from how we did
before: we used to say r30:35 which would mean "The difference between
the states in revision 30 and 35". Merge tracking talks about
revisions as r30-35 which means "The difference between the states in
revision 29 and 35".
I find this utterly confusing and even though several people have
argued that users think of revisions as changes, I don't think it's a
reason for us to start conflating the two.
Fortunately, we already have a 'change' concept: the 'c' option. If
we were to extend the syntax of the 'c' option to accept '-c30-35', I
would say the situation becomes less confusing, because then, the user
can enter commands exactly the way the command line client generates
its output.
bye,
Erik.
PS: I second C Mike's argument that we are currently giving confusing
output; maybe changing 'revision' to 'change' with revision number
arguments 'cX-Y' would be the best solution...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--- End Message ---
