Message-ID: <419B851B.5060202@arbash-meinel.com>
Date: Wed, 17 Nov 2004 11:06:35 -0600
From: John A Meinel <john@arbash-meinel.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
MIME-Version: 1.0
To: Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [Gnu-arch-users] Re: darcs vs tla
References: <20041116213258.GA16695@suffields.me.uk>
	<419A7430.8050300@mdl.com>	<77F65340-381A-11D9-A1EA-000A959B67D6@seyza.com>	<419ABADB.5020506@arbash-meinel.com>	<slrncpmsrq.68v.mark@localhost.localdomain>	<419B7885.9030903@arbash-meinel.com>	<slrncpmukm.68v.mark@localhost.localdomain>
	<1100710892.4124.16.camel@johannes>
In-Reply-To: <1100710892.4124.16.camel@johannes>
Cc: gnu-arch-users@gnu.org, Mark Stosberg <mark@summersault.com>
Precedence: list
Content-Type: multipart/mixed; boundary="===============1645975106=="
Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Status: RO
Content-Length: 2491
Lines: 84
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1645975106==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigE1A6E7E16E48658089547010"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigE1A6E7E16E48658089547010
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Johannes Berg wrote:
> On Wed, 2004-11-17 at 16:21 +0000, Mark Stosberg wrote:
> 
>>You can browse a "_darcs" directory of a small project here to obverse
>>the structure:
>>
>>http://mark.stosberg.com/darcs_hive/cgi-app/_darcs/
> 
> 
> The patches appear to be gzip compressed plain text files (dunno how it
> handles binary files), which already contain meta information (for
> example the comments). So I'd think adding a patch checksum that is
> signed would be trivial.
> 
> johannes
> 

See the comment by:
Juliusz Chroboczek <jch@pps.jussieu.fr>

It turns out that patches might be modified as part of applying them to 
your tree. (The whole idea of commutativity, etc for darcs.)

So patches aren't constant. Now, I wonder if they are constant after 
they are applied. (To apply a patch you might have to modify it, but 
don't after that.)

In that case, the patches could be signed, and then after they are 
applied, they are signed again by the new person.

A little bit of overhead, but still you could keep signatures on the 
patches.

I suppose you could also do something like include a signature history 
or something...

John
=:->


--------------enigE1A6E7E16E48658089547010
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD4DBQFBm4UbJdeBCYSNAAMRAlBEAKCpTMOLVY2TUQ22C9yc4meLkOeVzQCUDYTx
fAen1G21+ITMAFVe3q9UVQ==
=VXNT
-----END PGP SIGNATURE-----

--------------enigE1A6E7E16E48658089547010--


--===============1645975106==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gnu-arch-users mailing list
Gnu-arch-users@gnu.org
http://lists.gnu.org/mailman/listinfo/gnu-arch-users

GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/
--===============1645975106==--