On Mon, Sep 17, 2001 at 07:34:19AM -0500, Ben Collins-Sussman wrote:
> Mo DeJong <firstname.lastname@example.org> writes:
> > I am more interested in how the end user is going to go about
> > creating and applying patches with subversion. It is one of
> > the areas that CVS really punted on and it causes me no
> > end of grief in "day to day" work with CVS. The application
> > of changes to the WC is no different than the application of
> > changes from another branch. By pulling the "application of changes"
> > interface into an svn subcommand we free ourselves of a
> > lot of baggage.
> We are talking about the same thing, then: being able to easily
> produce *and* apply patches. And what I'm saying is that Subversion
> already does this. Currently, you can commit to an XML-patch file,
> and update from an XML-patch file. I sent a demo to this list
> recently. It only needs a few tweaks here and there.
I am still planning on working on this, but it is on hold for a little while,
until Change #6 (in STACK) gets implemented. Currently it would be _VERY_
difficult to generate unidiff format in an XML-patch, since all we have is
apply_textdelta. However, gstein assures me that this should be easier after
the push/pull thing is reversed.
In the meantime Mo, try svn ci --xml-file patch.xml. svn up --xml-file still
needs a little work (it currently always wants to bump revision numbers).
Kevin Pilch-Bisson http://www.pilch-bisson.net
"Historically speaking, the presences of wheels in Unix
has never precluded their reinvention." - Larry Wall
Received on Sat Oct 21 14:36:41 2006
- application/pgp-signature attachment: stored