lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 22 Jun 2017 12:35:13 -0300
From:   Mauro Carvalho Chehab <mchehab@...pensource.com>
To:     Pavel Machek <pavel@....cz>
Cc:     Patchwork <patchwork@...uxtv.org>, sakari.ailus@....fi,
        laurent.pinchart@...asonboard.com, linux-media@...r.kernel.org,
        mchehab@...nel.org, pali.rohar@...il.com, sre@...nel.org,
        kernel list <linux-kernel@...r.kernel.org>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        linux-omap@...r.kernel.org, tony@...mide.com, khilman@...nel.org,
        aaro.koskinen@....fi, ivo.g.dimitrov.75@...il.com,
        patrikbachan@...il.com, serge@...lyn.com, abcloriens@...il.com
Subject: Re: patchwork: on whose behalf is it working? was Re: [linux-media]
 Patch notification: 3 patches updated

Em Thu, 22 Jun 2017 17:19:03 +0200
Pavel Machek <pavel@....cz> escreveu:

> Hi!
> 
> 
> > The following patches (submitted by you) have been updated in patchwork:
> > 
> >  * linux-media: [RFC,07/13] v4l2: device_register_subdev_nodes: allow calling multiple times
> >      - http://patchwork.linuxtv.org/patch/39403/
> >      - for: Linux Media kernel patches
> >     was: New
> >     now: Accepted  
> 
> Dear patchwork, I'm not sure on who's behalf you are mailing me. (And
> that would be really nice to fix.)

Sorry, but patchwork is not smart enough to read and reply 
e-mails yet :-) It is just a dumb robot.

> If you are writing on Sakari's behalf, all is well.

> If you are writing on someone else's behalf, you may tell that
> someone to coordinate with Sakari, because he likely has it in his
> tree already.

>From the delatate to: field, it seems that Sakari was the one
that did the change...

However, patchwork is also dumb enough to not store any info
about who changed a status (or even to log it)...

Regards,

Thanks,
Mauro

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ