Front page | perl.perl5.porters |
Postings from January 2011
On Wed, Jan 5, 2011 at 7:37 PM, Jan Dubois <jand@activestate.com> wrote: > I don't know, the most common use case _should_ be that after you > have done a number of fresh commits you should head over to > cherymaint and immediately reject them for integration into maint > if you already know that they would not be allowed by perlpolicy.pod. Ick. Maybe if Porting/cherrymaint were modified to walk recent commits and let me send rejects. Jumping over to a web site to do that is a nasty break in my workflow. And, often, I'm not at a machine with a browser that can tunnel to the cherrymaint server. -- DavidThread Previous | Thread Next