On Wednesday 09 October 2002 17:24, Ben Collins-Sussman wrote:
> "LOWE,DAVID (HP-Vancouver,ex1)" <dave.lowe@hp.com> writes:
> > On Thursday Jack decides he needs Jill's Wednesday changeset and applies
> > it to his file. My "order independent changeset" would give Jack these
> > file contents.
> >
> > main()
> > {
> > Func1();
> > Func2();
> > Func3();
> > WednesdaysFunc(); /* Wednesday's changeset */
> > Func4();
> > JacksFunc(); /* Jack's changeset */
> > Func5();
> > }
> >
> > Can I get that from subversion?
>
> Sure. Jack reads the commit logs, and sees that Jane's Wednesday
> change created revision 53 when she committed. Revision 53 is not
> only the 53rd state of the repository, but it also represents a unique
> patch applied to the repository.
>
> Jack simply applies her change to his working copy using 'svn merge':
>
> svn merge -r52:53 path/to/project my/working/copy/path
>
> This means, "take the differences between revision 52 and 53 of
> path/to/project, and apply these differences as local modifications to
> my/working/copy/path."
>
So instead of "marshalling revisions into a blob" to pass them between
repositories, Jill can just tell Jack to grab changeset 53 (i.e. the unique
patch applied at rev 53) from her repos. He can then merge the changes into
his own repos whenever he feels like it. Right? Or am I missing the point of
revision blobs?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 10 00:47:23 2002