[PATCH 1/2] Use an explicit initial default patch state

[Dirk Wallenstein]

On Mon, Apr 30, 2012 at 09:57:04AM +0200, Wolfgang Denk wrote:
> Dear Jeremy,
> 
> In message <4F9E34EF.5030005 at ozlabs.org> you wrote:
> > 
> > > This will make editing states through the admin UI less error-prone, and
> > > will facilitate parsing patches when relying on a default state, as well as
> > > testing.
> > >
> > > Use the explicit default state when parsing mails.
> > >
> > > Signed-off-by: Dirk Wallenstein<halsmit at t-online.de>
> > 
> > 
> > Excellent, thanks for your work on these. I've committed and pushed, 
> > plus a couple of minor changes.
> > 
> > Wolfgang - these changes are now live the patchwork.ozlabs.org site too 
> > now :)
> 
> Thanks a lot!
> 
> Um... but is it really working?
> 
> I added "X-patchwork-state: Accepted" to a reply on a patch; my reply
> was correctly added to the respective PW entry
> (http://patchwork.ozlabs.org/patch/155545/) but the status did not
> change.
> 
> Am I doing something wrong?

You can only request an initial state (e.g. RFC) when submitting the
patch -- in the same mail as the patch.  Changing the state later on by
mail is problematic due to the lack of authentication, I'd say.  But you
can do that with pwclient.

-- 
Cheers,
  Dirk