Re: [tor-dev] Proposal 301: Don't include package fingerprints in consensus documents

2019-03-13 Thread teor
> On 14 Mar 2019, at 03:50, Iain Learmonth wrote: > > Signed PGP part > Hi, > >>> On 25/02/2019 23:30, teor wrote: Looks good to me, let's merge it as an "accepted" proposal? > > This is now proposal 301. > > What is the process by which this becomes "accepted"? Is this just a > matter

Re: [tor-dev] Proposal 301: Don't include package fingerprints in consensus documents

2019-03-13 Thread Iain Learmonth
Hi, >> On 25/02/2019 23:30, teor wrote: >>> Looks good to me, let's merge it as an "accepted" proposal? This is now proposal 301. What is the process by which this becomes "accepted"? Is this just a matter of someone making that commit? Thanks, Iain. signature.asc Description: OpenPGP