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

Re: Release, bindings (Was: svn commit: r12731 - trunk/notes)

From: Ben Reser <ben_at_reser.org>
Date: 2005-01-14 21:33:55 CET

On Fri, Jan 14, 2005 at 12:12:12PM -0800, Justin Erenkrantz wrote:
> I'm not exactly sure how multiple signatures would work in practice, but
> that'd be a fine way to record who has signed off on it. -- justin

IMHO this is how I'd handle this.

Create a new file somwhere (probably on the approriate branch) for
tracking the tarball. It'd probably similar to STATUS. People would
vote, leave comments, etc...

At the bottom of the file we'd have a section for each tarball/zip file
where people would append their signature which they made by doing:
gpg -b --armor subversion-1.1.x.tar.bz2
(and so on for the other files).

The .asc file that we ship can have multiple sigs and GPG will check
each one. So I would simply take and append all the sigs together into
the .asc file before final posting.

Ben Reser <ben@reser.org>
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 14 21:35:10 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.