[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r29789 - trunk/notes

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: Wed, 12 Mar 2008 09:18:20 -0400

On Tue, Mar 11, 2008 at 6:34 PM, Lieven Govaerts <svnlgo_at_mobsol.be> wrote:
>
> Justin Erenkrantz wrote:
> > On Tue, Mar 11, 2008 at 3:24 PM, Lieven Govaerts <svnlgo_at_mobsol.be> wrote:
> >> Wouldn't 'svn export' and a completely working 'svn patch <xml_patch>'
> >> do the same? The way you use working copies in this example looks more
> >> like a workaround for a missing feature than really needing a *working*
> >> copy.
> >
> > No - or at least I'm missing what you mean. In apache.org's case, we
> > have a shared directory that gets exported to our websites. A 'svn
> > patch' would absolutely not work - you want to publish the latest
> > version, not apply a patch... -- justin
> >
>
> I was referring to a patch format that can also delete & add directories
> etc. Isn't that what the svnpatch-diff branch is supposed to achieve?
>
> Anyway you still need to know the actual revision of the files on the
> target server to create the patch, might as well use a working copy then.

Exactly. While it might "work", it would be incredibly more error prone.

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-12 14:18:33 CET

This is an archived mail posted to the Subversion Dev mailing list.