* Greg Hudson (ghudson@MIT.EDU) wrote:
> Okay, now that I understand what people mean:
>
> In Subversion's own centralized way, it has changesets. Each revision
> knows what changes were made (possibly spanning many files), and the
> context to which that change was made (the previous revision).
>
> What it does not have is a way of marshalling revisions into a blob and
> passing them around between repositories. This is because Subversion
> lacks distributed repository functionality, not because it lacks
> changesets.
Full distributed repository functionality is a bit more than changesets.
The important thing is to be able to refer to a group of checkins by a
single name. Even if it is restricted to being on the same server as
the destination repository this is a long way along the path.
Now I can refer to a particular point on a branch by doing a 'cp' and
thus aliasing it; but for this what I need to do is have two points - a
before and after. Perhaps something as simple as having a
changeset start property is what is needed on a particular branch so
that you know automatically where to take the diff to?
Dave
---------------- Have a happy GNU millennium! ----------------------
/ Dr. David Alan Gilbert | Running GNU/Linux on Alpha,68K| Happy \
\ gro.gilbert @ treblig.org | MIPS,x86,ARM, SPARC and HP-PA | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 9 01:44:59 2002