On Sat, Sep 24, 2011 at 11:49:44AM +0200, m...@apollinemike.com wrote:
> What would be useful in git-cl is a way to signal to the
> PatchMeister the developer's perceived importance of a patch.
Current thinking is to automatically randomly pick 10 patch-review
for the countdown, with priority for
On Sep 24, 2011, at 11:39 AM, Graham Percival wrote:
> On Sat, Sep 24, 2011 at 11:16:35AM +0200, m...@apollinemike.com wrote:
>> Then they should not be put on a countdown - I'm not sure which patches of
>> mine will be review-ready by the time Colin sends out his weekly e-mail.
>
> It's thre
On Sat, Sep 24, 2011 at 11:16:35AM +0200, m...@apollinemike.com wrote:
>Then they should not be put on a countdown - I'm not sure which patches of
>mine will be review-ready by the time Colin sends out his weekly e-mail.
It's three times a week. There should be no rush to "get stuff
added
On Sep 24, 2011, at 4:27 AM, Graham Percival wrote:
> On Fri, Sep 23, 2011 at 09:43:01PM -0400, Colin Campbell wrote:
>> Instead, we present a special, one time only, batch as
>> requested by Mike Solomon.
>
> Am I correct that these have not been checked by James? I don't
> think we should c
On Fri, Sep 23, 2011 at 09:43:01PM -0400, Colin Campbell wrote:
> Instead, we present a special, one time only, batch as
> requested by Mike Solomon.
Am I correct that these have not been checked by James? I don't
think we should call this a "countdown". By all means suggest
that people review
FOR 21:00 MDT 20110925
As it happens, the one time I both travel (to my Mother's place across the
continent) *and* arrange to borrow a browser to cover my patch meister
schedule, there are no patches in the issue tracker ready to go. Instead, we
present a special, one time only, batch as requ
