Em Tue, 8 Oct 2019 00:16:42 +0200
Johan Herland escreveu:
> The V4L project (https://patchwork.linuxtv.org) uses patch states and
> delegates extensively to track progress. We want an audit log to keep
> track of the changes made to these patch fields. The Event model already
> records this info
Em Mon, 14 Oct 2019 08:26:37 -0400
"Theodore Y. Ts'o" escreveu:
> On Mon, Oct 14, 2019 at 12:42:36PM +0200, Toke Høiland-Jørgensen wrote:
> > It should be detectable, though, right?
> >
> > Say you have two independently administered patchwork instances (or even
> > better, two different softwar
Em Mon, 14 Oct 2019 09:53:58 -0400
"Theodore Y. Ts'o" escreveu:
> On Mon, Oct 14, 2019 at 10:41:32AM -0300, Mauro Carvalho Chehab wrote:
> > It can still have man-in-the-middle (MITM) attacks between the sender and
> > vger.kernel.org. Please notice that using http
Em Fri, 11 Oct 2019 11:32:54 -0700 (PDT)
David Miller escreveu:
> From: Steven Rostedt
> Date: Fri, 11 Oct 2019 14:01:08 -0400
>
> > Thus, if we want people to send us their fixes, we better keep just
> > an email with a patch the lowest bar for entry.
>
> I argue that for people coming into
Em Fri, 11 Oct 2019 14:44:01 -0400
Steven Rostedt escreveu:
> On Fri, 11 Oct 2019 11:32:54 -0700 (PDT)
> David Miller wrote:
>
> > From: Steven Rostedt
> > Date: Fri, 11 Oct 2019 14:01:08 -0400
> >
> > > Thus, if we want people to send us their fixes, we better keep just
> > > an email with
Em Thu, 10 Oct 2019 15:53:35 -0400
Konstantin Ryabitsev escreveu:
> On Thu, Oct 10, 2019 at 03:07:29PM -0300, Mauro Carvalho Chehab wrote:
> >> - the patch submission screen has a succession of screens:
> >>
> >> 1. a screen with a single field allowing a user to
Em Fri, 11 Oct 2019 11:20:17 -0600
Shuah Khan escreveu:
> On 10/11/19 2:57 AM, Greg KH wrote:
> > On Thu, Oct 10, 2019 at 10:41:50AM -0400, Konstantin Ryabitsev wrote:
> >> Hi, all:
> >>
> >> I would like to propose a new (large) feature to patchwork with the goal to
> >> make the process of su
Em Thu, 10 Oct 2019 10:41:50 -0400
Konstantin Ryabitsev escreveu:
> Hi, all:
>
> I would like to propose a new (large) feature to patchwork with the goal
> to make the process of submitting a patch easier for newbies and people
> generally less familiar with patch-based development. This was d
abase
using MySQL, but can easily changed to Postgres or to any other
DB.
Signed-off-by: Mauro Carvalho Chehab
-
PS.: By purpose, I didn't use Django here. It is a way easier for me to
write SQL commands directly than try to guess how to produce the
same results with Django. Also, I don
Mauro Carvalho Chehab
diff --git a/patchwork/filters.py b/patchwork/filters.py
index 79aaea437c6e..11d00390145a 100644
--- a/patchwork/filters.py
+++ b/patchwork/filters.py
@@ -385,6 +385,7 @@ class ArchiveFilter(Filter):
class DelegateFilter(Filter):
name = 'Delegate'
pa
https://linuxtv.org/patchwork_stats.php
>
> It requires pandas and matplotlib to work. It assumes a database
> using MySQL, but can easily changed to Postgres or to any other
> DB.
>
> Signed-off-by: Mauro Carvalho Chehab
>
> -
>
> PS.: By purpose, I didn't use Djan
Forwarded message:
Date: Tue, 4 Jun 2019 15:07:58 -0300
From: Mauro Carvalho Chehab
To: patchwork@lists.ozlabs.org
Subject: [PATCH v2] filters: re-add the possibility of filtering undelegated
patches
The filters.py redesign that happened for patchwork 1.1 removed
a functionality that we
Em Tue, 04 Jun 2019 12:39:49 +0100
Stephen Finucane escreveu:
> On Mon, 2019-06-03 at 23:34 -0300, Mauro Carvalho Chehab wrote:
> > Em Tue, 04 Jun 2019 10:10:51 +1000
> > Daniel Axtens escreveu:
> >
> > > Mauro Carvalho Chehab writes:
> > >
> &
Em Tue, 04 Jun 2019 10:10:51 +1000
Daniel Axtens escreveu:
> Mauro Carvalho Chehab writes:
>
> > The filters.py redesign that happened for patchwork 1.1 removed
> > a functionality that we use a lot: to filter patches that weren't
> > delegated to anyone.
> &
Mauro Carvalho Chehab
---
LinuxTV was using some pre-version 1.0 patchwork instance since
last week. Migrating was not easy, due to the delegation patches we
developed for 1.x, that caused the migration scripts to fail.
On Friday, we finally migrated to the latest stable version:
t as a regexp using a
> > > > custom validator.
> > > >
> > > > Signed-off-by: Laurent Pinchart
> > > > Signed-off-by: Mauro Carvalho Chehab
> > >
> > > Some small nits that I can fix myself. Other than that,
> >
> >
Em Thu, 24 Dec 2015 13:57:08 +
"Finucane, Stephen" escreveu:
> On 28 Nov 10:14, Mauro Carvalho Chehab wrote:
> > When a patch is delegated, it can be important to report it via
> > pwclient, as handing delegated patches may be different. So, add
> > an option
When things are broken at parsemail, we need to be able to
debug it. So, add some messages to it, in order to allow
checking what it actually did, and to let it return 1 if
an email got skipped by parsemail.
Signed-off-by: Mauro Carvalho Chehab
---
patchwork/bin/parsemail.py | 19
From: Laurent Pinchart
Delegation rules are used to automatically set the delegate of a patch
based on the files touched by the patch.
Signed-off-by: Laurent Pinchart
Signed-off-by: Mauro Carvalho Chehab
---
patchwork/admin.py | 9 -
patchwork/models.py | 8
2 files changed
the current value to be kept when editing the
patch.
Signed-off-by: Laurent Pinchart
Signed-off-by: Mauro Carvalho Chehab
---
patchwork/forms.py | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/patchwork/forms.py b/patchwork/forms.py
index 03279588a1ef
From: Laurent Pinchart
The function returns the list of files touched by a patch, after
stripping the leading component of the path name.
Signed-off-by: Laurent Pinchart
Signed-off-by: Mauro Carvalho Chehab
---
patchwork/parser.py | 34 ++
1 file changed, 34
From: Laurent Pinchart
The priority allows sorting delegation rules according to their
priorities. Higher priority rules will be evaluated first.
Signed-off-by: Laurent Pinchart
Signed-off-by: Mauro Carvalho Chehab
---
patchwork/admin.py | 2 +-
patchwork/models.py | 5 +
2 files
iority field to DelegationRule
parser: Use full regexps for delegation rules paths
Mauro Carvalho Chehab (4):
Report if a patch is delagated and to whom
views: make X-Patchwork-Delegate: to work again
Add delegate to migrations
parsemail: Add print messages to help debugging email pars
When a patch is delegated, it can be important to report it via
pwclient, as handing delegated patches may be different. So, add
an optional field at the email's body if this is happening.
Signed-off-by: Mauro Carvalho Chehab
---
patchwork/models.py
From: Laurent Pinchart
Signed-off-by: Laurent Pinchart
Signed-off-by: Mauro Carvalho Chehab
---
patchwork/bin/parsemail.py | 47 +++---
1 file changed, 40 insertions(+), 7 deletions(-)
diff --git a/patchwork/bin/parsemail.py b/patchwork/bin
Something broke the output of X-Patchwork-Delegate: via xmlrpc.
Fix it by moving the code to the xmlrpc part.
Signed-off-by: Mauro Carvalho Chehab
---
patchwork/models.py | 2 --
patchwork/views/__init__.py | 4
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a
Signed-off-by: Mauro Carvalho Chehab
---
patchwork/migrations/0001_initial.py | 24
1 file changed, 24 insertions(+)
diff --git a/patchwork/migrations/0001_initial.py
b/patchwork/migrations/0001_initial.py
index 65d1c3556414..5b71f3ef5385 100644
--- a/patchwork
From: Laurent Pinchart
Paths are validated by trying to compile it as a regexp using a custom
validator.
Signed-off-by: Laurent Pinchart
Signed-off-by: Mauro Carvalho Chehab
---
patchwork/bin/parsemail.py | 19 +--
patchwork/models.py| 9 -
2 files changed
Hi Stephen,
Em Fri, 06 Nov 2015 20:29:34 +
"Finucane, Stephen" escreveu:
> On 06 Nov 16:38, Mauro Carvalho Chehab wrote:
> > Em Fri, 06 Nov 2015 19:02:31 +0100
> > Johannes Berg escreveu:
> >
> > > > If not, then we're going to have (a) roll
Hi Don,
Em Mon, 09 Nov 2015 11:22:50 -0500
Don Zickus escreveu:
> On Fri, Nov 06, 2015 at 07:02:31PM +0100, Johannes Berg wrote:
> > +Konstantin, the kernel.org sysadmin. The context is that patchwork has
> > just removed (see subject) support for Django 1.6, but I've been told
> > that RHEL/EPE
Em Fri, 06 Nov 2015 20:41:20 +
"Finucane, Stephen" escreveu:
> On 06 Nov 15:57, Mauro Carvalho Chehab wrote:
> > Em Fri, 6 Nov 2015 15:52:02 +
> > Damien Lespiau escreveu:
> >
> > > On Fri, Nov 06, 2015 at 12:25:18PM -0200, Mauro Carvalho Chehab
Em Fri, 06 Nov 2015 19:02:31 +0100
Johannes Berg escreveu:
> > If not, then we're going to have (a) roll back the Django 1.6 removal
> > patches, (b) put together a roadmap for future Django version support and
> > (c) avoid using non-stdlib libraries (outside of Django) going forward. As
> > Dam
Em Fri, 06 Nov 2015 17:37:47 +
"Finucane, Stephen" escreveu:
> > On Fri, Nov 06, 2015 at 12:25:18PM -0200, Mauro Carvalho Chehab wrote:
> > > > Django 1.8 is LTS so I imagine there should be support coming for this
> > in
> > > > EPEL, SLES etc.
Em Fri, 6 Nov 2015 15:52:02 +
Damien Lespiau escreveu:
> On Fri, Nov 06, 2015 at 12:25:18PM -0200, Mauro Carvalho Chehab wrote:
> > > Django 1.8 is LTS so I imagine there should be support coming for this in
> > > EPEL, SLES etc. I'm little to no experience
Hi Stephen,
Em Thu, 5 Nov 2015 18:18:36 +
"Finucane, Stephen" escreveu:
> The problem with continuing support for Django 1.6 is, as mentioned, that
> it incurs a huge amount of overhead due to the SQL migrations (this affects
> not only developers but also sysadmins, who must validate and
Em Tue, 21 Jul 2015 10:49:43 +0200
Thomas Monjalon escreveu:
> 2015-07-21 10:45, Thomas Petazzoni:
> > On Tue, 21 Jul 2015 08:17:56 +, Finucane, Stephen wrote:
> > > Finally, would the non-maintainers be able to set state to any state.
> > > In Gerrit, the submitter of a patch can abandon or
Em Wed, 26 Nov 2014 13:42:21 +0800
Jeremy Kerr escreveu:
> Hi all,
>
> > On Mon, Nov 24, 2014 at 05:35:11PM +, Damien Lespiau wrote:
> >> I'd like to be able to assign reviewers to patches. That seems very
> >> close to what a delegate is today. Would anyone have objections if I
> >> just us
Em Sun, 23 Nov 2014 09:34:34 +0100
Wolfram Sang escreveu:
> Hi,
>
> displaying this patch is broken in the web interface:
>
> http://patchwork.ozlabs.org/patch/413335/
>
> Only one hunk is displayed as a patch, the other hunk as a comment.
>
> Would be great if somebody could have a look.
We
Em Fri, 7 Feb 2014 14:52:52 -0800
Markus Mayer escreveu:
> On 7 February 2014 14:37, Wolfram Sang wrote:
> > On Fri, Feb 07, 2014 at 11:06:39PM +0100, Carl-Daniel Hailfinger wrote:
> >> Am 06.02.2014 23:49 schrieb Markus Mayer:
> >> > Make sure we don't attempt to search for a patch in a reply e
Em Fri, 17 May 2013 12:23:05 +0200
Wolfram Sang escreveu:
> Hi,
>
> I noticed that the project name is not included in the
> patch-update-notification-mail. I guess this could be useful in case one
> patch has been sent to multiple lists. Pseudo patch follows.
Actually, I would rather prefer to
Hi Jeremy,
What criteria are used to allow someone to create a new account on patchwork?
What I'm seeing on my patchwork instance is that there are thousands of
what it seems to be fake accounts there, like:
http://patchwork.linuxtv.org/project/linux-media/list/?submitter=4392&state=*
Em Fri, 15 Feb 2013 18:34:16 +0100
Wolfram Sang escreveu:
> Doug,
>
> > As far as I can tell, patchwork creates a "submitter" for each email
> > address. Once it has decided on the name associated with a submitter
> > it doesn't change it. So the problem was actually with James' first
> > patc
Em Fri, 21 Dec 2012 09:23:30 +0800
Jeremy Kerr escreveu:
> Hi Doug,
>
> > Add a new filter option '-r' that attempts to list all patches in a
> > series. Since there's no built-in way in patman to do this, we use
> > some heuristics to try to find the series.
>
> Interesting idea, something I'
Em Thu, 20 Dec 2012 13:06:07 -0800
Doug Anderson escreveu:
> Add a new filter option '-r' that attempts to list all patches in a
> series. Since there's no built-in way in patman to do this, we use
> some heuristics to try to find the series.
Instead of adding it at the client level, IMHO, it w
Hi Jeremy,
The current rejex expression to catch pull requests are missing URL's
with ssh and git+ssh.
Could you please change it to also accept the other supported URL types?
If missing a patch is bad, it is even worse to miss a pull requests ;)
Thanks,
Mauro
__
Em 15-06-2011 10:11, Jeremy Kerr escreveu:
> Hi Albert,
>
>> (and I'll post an UTF-8-to-ISO-8859 fixup patch at the next merge window)
>
> Now, that's where it gets tricky - the patch you send will have *both*
> encodings in it.
>
> I'd suggest checking patchwork after sending it. Or even sendin
Em 29-04-2011 00:09, Jeremy Kerr escreveu:
> Hi Mauro,
>
>>> For ubuntu-kernel, when proposing an update patch, we forward the entire
>>> commit (possibly with comments before it, like why we're proposing the
>>> patch for that ubuntu kernel version). In this case, it'd be correct to
>>> parse the
Em 28-04-2011 23:10, Jeremy Kerr escreveu:
> Hi Guilherme,
>
>> When the first line of the email message that contains a patch starts with
>> 'From:' and contain an email address, we use that address as the author;
>> otherwise we use the same as the submitter.
>>
>> Currently this information is
Em 30-03-2011 08:56, Alasdair G Kergon escreveu:
> On Wed, Mar 30, 2011 at 03:28:18PM +0800, Jeremy Kerr wrote:
>> However (as you say in your second point), all maintainers currently have
>> permissions to edit the state of all patches. To deal with this, it would be
>> feasible to (set by a per
Em 30-03-2011 04:28, Jeremy Kerr escreveu:
> Hi Mauro,
>
>> 1) I'm using kernel.org facilities for Patchwork. As a project owner, I
>> cannot give anyone else any extra permission. I'm forced to contact
>> kernel.org manager, if I want do do it;
>
> This is what I'm planning to address: allow 'le
Hi Jeremy,
There is one thing at Patchwork that imposes a very high overload on
my knees: the lack of a proper way to delegate work to project collaborators.
I receive more than 1,000 patches per Kernel cycle, and manage about 300
different
drivers, with 20+ driver maintainers. Yet, I have to ma
Em 18-03-2011 19:13, Guilherme Salgado escreveu:
> On Fri, 2011-03-18 at 22:43 +0100, Peter Maydell wrote:
>> On 18 March 2011 22:33, Guilherme Salgado
>> wrote:
>>> On Fri, 2011-03-18 at 09:23 -0300, Mauro Carvalho Chehab wrote:
>>>> Em 17-03-2011 19:2
Em 17-03-2011 19:20, Peter Maydell escreveu:
> On 17 March 2011 23:06, Guilherme Salgado
> wrote:
>> On Wed, 2011-03-16 at 13:50 -0300, Mauro Carvalho Chehab wrote:
>>> Em 16-03-2011 11:03, Guilherme Salgado escreveu:
>>>> I see that some emails with patches
Em 16-03-2011 11:03, Guilherme Salgado escreveu:
> Hi there,
>
> I see that some emails with patches have a From: field in the body[1],
> and I'm wondering if there's any reason for not using that (when
> available, of course) as the patch submitter. Well, now that I think of
> it, one could argu
Em 12-12-2010 22:58, Jeremy Kerr escreveu:
> Hi Mauro,
>
>> I never used it, nor I am a python expert, but it sems that django defines
>> a class of lazy utf decoders that won't cause python to crash due to a
>> string that it is not following the proper encoding:
>> http://docs.djangoproject
Em 10-12-2010 05:10, Jeremy Kerr escreveu:
> Hi Wolfgang,
>
>>> I think a number of messages have special characters in iso8859-1 and
>>> iso8859-9.
>>>
>>> A n option would not really help. I'm running into this when
>>> auto-updating the status of some patches using a script similat to
>>> what
Again, I got trapped by the lack of the history when getting the patches via
pwclient.
On the last recent case, this patch:
https://patchwork.kernel.org/patch/91888/
Is clearly not ready for merge, when looking via web, but if you get the patch
via
pwclient view, it gets:
Conten
martin f krafft wrote:
> also sprach Mauro Carvalho Chehab [2010.02.11.1259
> +1300]:
>>>> For a replacement patch, you may try to use an algorithm like
>>>> what -git does: get only the diff and compare the previous and
>>>> the new version. If
martin f krafft wrote:
> also sprach Mauro Carvalho Chehab [2010.02.10.2344
> +1300]:
>>> So detecting this relation automatically is kinda difficult,
>>> based only on the threading info.
>> If the follow-up patch has the in-reply-to, you can use the patch
>
Jeremy Kerr wrote:
> Hi Martin,
>
>> In fact, it seems that Patchwork sometimes just screws up.
>>
>> http://notmuchmail.org/pipermail/notmuch/2010/001439.html was sent
>> in direct reply to
>> http://notmuchmail.org/pipermail/notmuch/2010/001438.html, but
>> Patchwork still generated http://patch
Hi Jeremy,
Em Tue, 22 Sep 2009 22:36:25 -0700
Jeremy Kerr escreveu:
> This could be for a few reasons; most often it's a character-set encoding
> problem with the patch
The way python was written, it imposes a penalty to everyone with accents on
their names. In the case of patchwork, this happ
ror: 'ascii' codec can't encode character u'\ufeff' in
> > position 256: ordinal not in range(128)
> >
I think I've already sent a patch for it. Anyway, Let's sent it back.
-
Fix yet-another issue with pwclient not working with utf-8 chars
Sign
62 matches
Mail list logo
