I agree on the overall validity of the idea... just a question tho...
inline...
On Thu, 2005-10-27 at 17:49, Julian Foad wrote:
> Some thoughts on the introduction of the "--change" ("-c") option.
>
> This is important. It is not just a little syntax tweak. It gives us a way to
> express a concept directly that has hitherto only been implied. We need to be
> comfortable with this.
>
> This finally enables us to resolve some of the confusion between "revision"
> meaning "a snapshot or version of the managed tree" (as in "svn cat -r10") and
> "revision" meaning "the change from one version to another" (as in "svn log
> -r10"). We can keep "revision" and the option "-r" for the former, as that is
> what it usually means, but express the latter concept with this new option
> "-c"/"--change".
>
> Here is how changes and versions fit together through time (ASCII art):
>
> Time Changes Versions
>
> | ----------------------------+
> v / |
> | +---------------------------- r0: The empty tree. |
> | | \ |
> v | Commit 1: time, author, ----------------------------+
> | | log message / |
> | +---------------------------- r1: The first version. |
> v | \ |
> | | Commit 2: time, author, ----------------------------+
> | | log message / |
> v +---------------------------- r2: The second version. |
> | \ |
> v ----------------------------+
>
> I looked through the "svn" subcommands. Most of those that take "--revision"
> conceptually operate on a version. These few are the exceptions:
>
> * diff, merge: These can usefully be enhanced to accept a single "change" as a
> special case of their general operation on the difference between one revision
> and another.
the diff accepts a '-c 10,20' too? or only '-c 10:20'? or maybe only '-c
10' ? could you pl. elaborate?
Regards,
Madan.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 27 20:47:54 2005