Front page | perl.perl5.porters |
Postings from January 2011
On Wed, 05 Jan 2011, Ricardo Signes wrote: > * Vincent Pit <perl@profvince.com> [2011-01-05T18:33:45] > > I've already added some new features to cherrymaint in my github > > fork, like > > - immediate JS update of votes ; > > - a "to be discussed" grade ; > > - only display $n commits by page (the complete page takes ages to > > load currently). > > Am I the only one who would rather the commits were in reverse of > their current order, so that when reading from the top you would view > them in to-pick order to match blead? 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. So having the last commits on top works best for that case. BTW, as long as we are in wishlist mode, I have thought more than once that it would be good to hide all commits in cherrymaint that are already rejected or cherry-picked because there isn't much point to look at them again (most of the time). I didn't want it badly enough to offer to implement it though. :) Cheers, -JanThread Previous | Thread Next