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

Re: makepatch/applypatch beyond diff/patch

From: Andreas J. Koenig <andreas.koenig_at_anima.de>
Date: 2002-11-26 06:15:18 CET

>>>>> On 25 Nov 2002 17:30:37 -0600, Karl Fogel <kfogel@newton.ch.collab.net> said:

> Karl Fogel <kfogel@newton.ch.collab.net> writes:
>> Am taking a look; folks, note that a full URL is
>> http://www.perl.com/CPAN-local/modules/by-authors/id/J/JV/JV/makepatch-2.00_09.tar.gz

> Took a look. Seems like a useful program... but unfortunately, it
> doesn't document the patchkit format. Maybe that's a pre-existing
> convention that's documented somewhere else?

I think that makepatch is as old as patch itself and the format is a
single-implementation de facto standard. I don't know if Johan has
ever tried to write the specs down.

> The important question for Subversion is whether the format is
> extensible, so we can put metadata (properties) into the patchkits
> without making them incompatible with `applypatch'. Do you happen to
> know the answer?

Maybe: currently, when I use makepatch on subversioned directories, I
use the '--exclude .svn' option. Depending on how properties are
stored within the .svn directories, it might be possible to include
some parts of the .svn directory and that's it. That would boil down
to a single option.

Otherwise, if you need access to the applypatch metadata directly, you
need to ask Johan, if there is room for an extension mechanism.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 26 06:16:16 2002

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