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

Re: svn commit: r516 - /dev/subversion/subversion-1.7.4.zip.asc

From: Daniel Shahaf <danielsh_at_elego.de>
Date: Fri, 2 Mar 2012 10:08:04 +0200

Justin Erenkrantz wrote on Thu, Mar 01, 2012 at 23:43:41 -0800:
> On Thu, Mar 1, 2012 at 4:59 PM, <markphip_at_apache.org> wrote:
> > Author: markphip
> > Date: Fri Mar  2 00:59:05 2012
> > New Revision: 516
> >
> > Log:
> > Add my signature to zip file
> >
> > Modified:
> >    dev/subversion/subversion-1.7.4.zip.asc
>
> Is there a particular reason these new commit notices are going to
> dev@ and not to commits@?
>

My idea was to maintain the status quo whereby whenever someone signs
the tarballs he also mails dev@ saying so.

> I realize that I might be stumbling into a bikeshed - however, I don't
> recall seeing a conversation as to why we want these on dev@ or really

http://svn.haxx.se/dev/archive-2012-02/0448.shtml

> even seeing these notices for a release before. (My take is that the

We didn't use the dist/ repository for releases before; Hyrum collected
sigs out-of-band using a CGI (tools/dist/collect_sigs.py) running on his
private box.

> people interested in following commit traffic are also going to be
> interested in release preps/sigs too; and the less traffic on dev@,
> the better, IMO.) -- justin

I'm happy to change the setting here as people want.

Cheers,

Daniel
Received on 2012-03-02 09:09:01 CET

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.