Paul Berry writes:
> I just pushed some patches to piglit and mesa, and the script seems to be
> working well now. Thanks for all your hard work on this, Carl!
Cool! When I saw the subject of your mail, I was afraid something wasn't
working again. I'm glad to know it's all working.
> Anyway, it
On 5 December 2013 11:33, Carl Worth wrote:
> Carl Worth writes:
> > So, you should all expect to see these hook messages now:
> >
> >> remote: I: patch # updated using rev .
> > ...
> >> remote: E: failed to find patch for rev .
>
> For anyone who has pushed patches for the past coupl
Carl Worth writes:
> So, you should all expect to see these hook messages now:
>
>> remote: I: patch # updated using rev .
> ...
>> remote: E: failed to find patch for rev .
For anyone who has pushed patches for the past couple of days, you
likely only saw the "failed to find patch" mes
Carl Worth writes:
> When a branch is pushed to the master git repo, a git hook will
> automatically search for the patch in the database, and if it is
> found,
...
At least, that was my intention.
I had a couple of permissions problem with the git hook, so it hasn't
actually been active. I fix
For those of you who don't know, freedesktop.org runs an instance of
Patchwork to aid in tracking patches that are in need of review. We've
just finished getting it integrated with the Mesa-dev list. Here's a
brief run-down of what Patchwork provides for us.
Automatic flow of patches in Patchwork
