Hi Veronika,
Apologies for the delay in getting back to you, and thanks for your responses.
>> Consider a list like netdev. It has at least a couple of userspace
>> projects (iproute2, ethtool) that could conceivably be spun off into
>> their own lists, and which could use subject matches, but m
- Original Message -
> From: "Daniel Axtens"
> To: vkaba...@redhat.com, patchwork@lists.ozlabs.org
> Sent: Monday, February 5, 2018 4:24:21 PM
> Subject: Re: [PATCH] Implement list filtering
>
> Hi Veronika,
>
> So, having been convinced of the merit
On Tue, Feb 06, 2018 at 02:24:21AM +1100, Daniel Axtens wrote:
> Hi Veronika,
>
> So, having been convinced of the merits of this approach, here's my code
> review.
>
> > Sometimes, multiple projects reside at the same mailing list. So far,
> > Patchwork only allowed a single project per mailing
Hi Veronika,
So, having been convinced of the merits of this approach, here's my code
review.
> Sometimes, multiple projects reside at the same mailing list. So far,
> Patchwork only allowed a single project per mailing list, which made it
> impossible for these projects to use Patchwork (unless
Hi all,
>> To be honest, given how simple and generic this patch is, I'd prefer to
>> keep the logic within Patchwork. It would require much less work on an
>> administrators end over all (seeing as they'll have to configure
>> procmail too), and be far more transparent to end users.
>>
>
> I agr
- Original Message -
> From: "Stephen Finucane"
> To: "Daniel Axtens" , "Don Zickus"
> Cc: patchwork@lists.ozlabs.org
> Sent: Wednesday, January 31, 2018 11:25:03 AM
> Subject: Re: [PATCH] Implement list filtering
>
> On Wed, 2018
On Wed, 2018-01-31 at 13:25 +1100, Daniel Axtens wrote:
> Don Zickus writes:
>
> > On Mon, Jan 29, 2018 at 11:36:36PM +1100, Daniel Axtens wrote:
> > > Hi Don,
> > >
> > > > > I suppose to put a finer point on it - what is your usecase here? What
> > > > > are you trying to achieve, and can we h
Don Zickus writes:
> On Mon, Jan 29, 2018 at 11:36:36PM +1100, Daniel Axtens wrote:
>> Hi Don,
>>
>> >> I suppose to put a finer point on it - what is your usecase here? What
>> >> are you trying to achieve, and can we help you do that in a way that
>> >> requires smaller changes to Patchwork, a
On Mon, Jan 29, 2018 at 11:36:36PM +1100, Daniel Axtens wrote:
> Hi Don,
>
> >> I suppose to put a finer point on it - what is your usecase here? What
> >> are you trying to achieve, and can we help you do that in a way that
> >> requires smaller changes to Patchwork, and is less fragile? (For exa
Hi Don,
>> I suppose to put a finer point on it - what is your usecase here? What
>> are you trying to achieve, and can we help you do that in a way that
>> requires smaller changes to Patchwork, and is less fragile? (For example
>> this is going to break if someone mis-spells the keyword you're l
On Thu, Jan 25, 2018 at 05:57:47PM +1100, Daniel Axtens wrote:
> vkaba...@redhat.com writes:
>
> > From: Veronika Kabatova
> >
> > Sometimes, multiple projects reside at the same mailing list. So far,
> > Patchwork only allowed a single project per mailing list, which made it
> > impossible for t
vkaba...@redhat.com writes:
> From: Veronika Kabatova
>
> Sometimes, multiple projects reside at the same mailing list. So far,
> Patchwork only allowed a single project per mailing list, which made it
> impossible for these projects to use Patchwork (unless they did some
> dirty hacks).
>
> Add
From: Veronika Kabatova
Sometimes, multiple projects reside at the same mailing list. So far,
Patchwork only allowed a single project per mailing list, which made it
impossible for these projects to use Patchwork (unless they did some
dirty hacks).
Add a new property `subject_match` to projects
13 matches
Mail list logo
