On 26.09.2022 16:26, Andriy Gelman wrote:
On Mon, 26. Sep 14:46, Marvin Scholz wrote:
As I am not sure who else to email about this, I'll just post it here.
I tried to register for Patchwork, however I got an error when registering.
I tried again and was told the account already exists, I tried
On Mon, Sep 26, 2022 at 10:26:45AM -0400, Andriy Gelman wrote:
> On Mon, 26. Sep 14:46, Marvin Scholz wrote:
> > As I am not sure who else to email about this, I'll just post it here.
> >
> > I tried to register for Patchwork, however I got an error when registering.
> > I tried again and was told
On Mon, 26. Sep 14:46, Marvin Scholz wrote:
> As I am not sure who else to email about this, I'll just post it here.
>
> I tried to register for Patchwork, however I got an error when registering.
> I tried again and was told the account already exists, I tried to reset the
> password for the acco
On Mon, 26 Sep 2022, Marvin Scholz wrote:
As I am not sure who else to email about this, I'll just post it here.
I tried to register for Patchwork, however I got an error when registering.
I tried again and was told the account already exists, I tried to reset the
password for the account but d
> -Original Message-
> From: ffmpeg-devel On Behalf Of Soft Works
> Sent: Friday, January 21, 2022 5:52 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] Patchwork FATE Errors
>
>
>
> > -Original Message-
> &
> -Original Message-
> From: ffmpeg-devel On Behalf Of Andriy
> Gelman
> Sent: Friday, January 21, 2022 5:24 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] Patchwork FATE Errors
>
> On Fri, 21. Jan
On Fri, 21. Jan 01:44, Soft Works wrote:
>
>
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of Andreas
> > Rheinhardt
> > Sent: Friday, January 21, 2022 2:31 AM
> > To: ffmpeg-devel@ffmpeg.org
> > Subject: Re: [FFmpeg-devel]
> -Original Message-
> From: ffmpeg-devel On Behalf Of Andreas
> Rheinhardt
> Sent: Friday, January 21, 2022 2:31 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] Patchwork FATE Errors
>
> Soft Works:
> >
> >
> >> -Orig
Soft Works:
>
>
>> -Original Message-
>> From: ffmpeg-devel On Behalf Of Andreas
>> Rheinhardt
>> Sent: Thursday, January 20, 2022 11:38 PM
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: Re: [FFmpeg-devel] Patchwork FATE Errors
>>
&
> -Original Message-
> From: ffmpeg-devel On Behalf Of Andreas
> Rheinhardt
> Sent: Thursday, January 20, 2022 11:38 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] Patchwork FATE Errors
>
> Soft Works:
> >
> >
> >> -Orig
Soft Works:
>
>
>> -Original Message-
>> From: ffmpeg-devel On Behalf Of Andreas
>> Rheinhardt
>> Sent: Thursday, January 20, 2022 10:22 PM
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: Re: [FFmpeg-devel] Patchwork FATE Errors
>>
>> So
> -Original Message-
> From: ffmpeg-devel On Behalf Of Andreas
> Rheinhardt
> Sent: Thursday, January 20, 2022 10:22 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] Patchwork FATE Errors
>
> Soft Works:
> >
> > andriy/make_fate_ppc
&g
Soft Works:
>
> andriy/make_fate_ppc
>
> => Does it possibly need 'make fate-rsync'?
>
No. The test does not rely on need samples; and the other test that uses
this sample works fine. Some time ago, someone else wrote FATE tests for
AVDOVIDecoderConfigurationRecord in Matroska
(https://patchwor
On Mon, 16. Aug 20:42, Michael Niedermayer wrote:
> On Sun, Aug 15, 2021 at 01:53:23PM -0400, Andriy Gelman wrote:
> > On Sun, 15. Aug 17:15, Michael Niedermayer wrote:
> > > On Sun, Aug 15, 2021 at 08:18:17AM -0400, Andriy Gelman wrote:
> > > > On Sun, 15. Aug 11:17, Nicolas George wrote:
> > > >
On Sun, Aug 15, 2021 at 01:53:23PM -0400, Andriy Gelman wrote:
> On Sun, 15. Aug 17:15, Michael Niedermayer wrote:
> > On Sun, Aug 15, 2021 at 08:18:17AM -0400, Andriy Gelman wrote:
> > > On Sun, 15. Aug 11:17, Nicolas George wrote:
> > > > Is it possible to add hooks in Patchwork to warn people au
On Sun, 15. Aug 16:04, Nicolas George wrote:
> Andriy Gelman (12021-08-15):
> > That sounds fine.
>
> See the attached code.
>
> I have tested it against the 2721 commits I have since the beginning of
> the year, it finds 56 to object, about half of them real problems, a few
> with unusually lon
On Sun, 15. Aug 17:15, Michael Niedermayer wrote:
> On Sun, Aug 15, 2021 at 08:18:17AM -0400, Andriy Gelman wrote:
> > On Sun, 15. Aug 11:17, Nicolas George wrote:
> > > Is it possible to add hooks in Patchwork to warn people automatically
> > > when their commit message does not match standards?
>
On Sun, Aug 15, 2021 at 08:18:17AM -0400, Andriy Gelman wrote:
> On Sun, 15. Aug 11:17, Nicolas George wrote:
> > Is it possible to add hooks in Patchwork to warn people automatically
> > when their commit message does not match standards?
> >
> > If it is possible, I volunteer to write it.
> >
>
Andriy Gelman (12021-08-15):
> That sounds fine.
See the attached code.
I have tested it against the 2721 commits I have since the beginning of
the year, it finds 56 to object, about half of them real problems, a few
with unusually long context (I set the limit at the last percentile) and
admitt
Lynne (12021-08-15):
> Oh, that's all fine. I was talking about the change to the developer manual,
> about adding patch descriptions. Sometimes, you just don't need any.
The change I proposed says: "then if necessary a body with details".
Do you think it would be better if the "if necessary" par
15 Aug 2021, 13:39 by geo...@nsup.org:
> Lynne (12021-08-15):
>
>> Could you acknowledge that at least some commits do not deserve
>> mandatory 3-line vapid comments?
>>
>
> I have no idea what you are talking about.
>
> The hook I am suggesting would catch:
>
> - cases without "context:" on the f
On Sun, 15. Aug 14:22, Nicolas George wrote:
> Andriy Gelman (12021-08-15):
> > Yes, nice idea.
> >
> > If the commit message is invalid I could add a warning similar to:
> > https://patchwork.ffmpeg.org/project/ffmpeg/patch/20210809102919.387-1-an...@khirnov.net/
> > and trigger an automated emai
Andriy Gelman (12021-08-15):
> Yes, nice idea.
>
> If the commit message is invalid I could add a warning similar to:
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/20210809102919.387-1-an...@khirnov.net/
> and trigger an automated email to the author.
>
> Feel free to send me the parsing pa
On Sun, 15. Aug 11:17, Nicolas George wrote:
> Is it possible to add hooks in Patchwork to warn people automatically
> when their commit message does not match standards?
>
> If it is possible, I volunteer to write it.
>
Yes, nice idea.
If the commit message is invalid I could add a warning sim
Nicolas George:
> Michael Niedermayer (12021-08-15):
>> We could also add a fate test that checks the commit messages between
>> master (if == HEAD) and origin
>> iam not sure if people want this but it could eliminate some bad messages
>> before even reaching the mailing list (if the developer did
Michael Niedermayer (12021-08-15):
> We could also add a fate test that checks the commit messages between
> master (if == HEAD) and origin
> iam not sure if people want this but it could eliminate some bad messages
> before even reaching the mailing list (if the developer did run make fate)
I am
Lynne (12021-08-15):
> Could you acknowledge that at least some commits do not deserve
> mandatory 3-line vapid comments?
I have no idea what you are talking about.
The hook I am suggesting would catch:
- cases without "context:" on the first line, like:
[FFmpeg-devel] [PATCH] Handle AV_PIX_FM
15 Aug 2021, 11:49 by mich...@niedermayer.cc:
> On Sun, Aug 15, 2021 at 11:17:26AM +0200, Nicolas George wrote:
>
>> Is it possible to add hooks in Patchwork to warn people automatically
>> when their commit message does not match standards?
>>
>> If it is possible, I volunteer to write it.
>>
>
>
On Sun, Aug 15, 2021 at 11:17:26AM +0200, Nicolas George wrote:
> Is it possible to add hooks in Patchwork to warn people automatically
> when their commit message does not match standards?
>
> If it is possible, I volunteer to write it.
We could also add a fate test that checks the commit messag
I have the same problem. Hopefully someone with access is able to fix it.
> On Jul 26, 2019, at 4:38 AM, Andreas Håkon
> wrote:
>
> Hi,
>
> I'm sorry to post this on this mailing list. However, I need to clean my
> patches
> on the Patchwork's FFmpeg server, but the "Reset Password" service d
On Fri, Apr 19, 2019, at 2:15 PM, Hendrik Leppkes wrote:
>
> The first mail like that arrived, and handling of it of course
> depends on the mail client in question. But at least Patchwork doesn't
> seem to like it much, it quite simply still attributes it to the
> "shared" mail.
> Not sure if th
On Fri, Apr 19, 2019 at 8:23 PM Lou Logan wrote:
>
> On Thu, 18 Apr 2019 18:01:27 -0400
> "Lou Logan" wrote:
> >
> > But we can certainly give it a try if you like. I'm not sure how patchwork
> > will handle it.
>
> (Didn't realize my webmail client wasn't actually wrapping my text
> although it
On Thu, 18 Apr 2019 18:01:27 -0400
"Lou Logan" wrote:
>
> But we can certainly give it a try if you like. I'm not sure how patchwork
> will handle it.
(Didn't realize my webmail client wasn't actually wrapping my text
although it was doing it in the window at the expected lengths.)
I just chang
On Fri, 19 Apr 2019 00:05:00 +
Andreas Rheinhardt wrote:
> But now I am unsure whether I should resend my patchsets?
At this point I suggest resending as it will allow the commiter to
avoid having to adjust the author and will help avoid mistakes.
Hello,
Gyan:
>
> Patchwork can incorrectly assign ownership. See
> https://patchwork.ffmpeg.org/patch/12680/
>
> The author is Sam John as identified by Message ID as well as the From
> field in the headers, yet Patchwork attributes this patch to "Oliver
> Collyer via ffmpeg-devel", a name which
On Thu, Apr 18, 2019, at 1:25 PM, Hendrik Leppkes wrote:
>
> Did you try the "wrap" option? As I understand it, it would preserve
> the original mail entirely, and rely on the mail client of the
> recipient (ie. us) to properly unwrap the MIME container.
> We've had various problems of authorship i
On Thu, Apr 18, 2019 at 9:04 PM Lou Logan wrote:
>
> On Thu, Apr 18, 2019, at 4:51 AM, Hendrik Leppkes wrote:
> >
> > Whoever setup this ML sender rewriting thing should probably look into
> > options to also re-write the patch content and add a "From:" line in
> > there with the original name and
On Thu, Apr 18, 2019 at 03:03:44PM -0400, Lou Logan wrote:
> On Thu, Apr 18, 2019, at 4:51 AM, Hendrik Leppkes wrote:
> >
> > Whoever setup this ML sender rewriting thing should probably look into
> > options to also re-write the patch content and add a "From:" line in
> > there with the original n
On Thu, Apr 18, 2019, at 4:51 AM, Hendrik Leppkes wrote:
>
> Whoever setup this ML sender rewriting thing should probably look into
> options to also re-write the patch content and add a "From:" line in
> there with the original name and email to avoid issues.
I enabled this due DMARC as Timo corr
On 18-04-2019 07:03 PM, Hendrik Leppkes wrote:
On Thu, Apr 18, 2019 at 3:31 PM Gyan wrote:
On 18-04-2019 06:13 PM, Hendrik Leppkes wrote:
All of those patches with re-written senders are send from the same
email, ffmpeg-devel@ffmpeg.org
Presumably patchwork only sends the email itself, no
On Thu, Apr 18, 2019 at 3:31 PM Gyan wrote:
>
>
>
> On 18-04-2019 06:13 PM, Hendrik Leppkes wrote:
> > On Thu, Apr 18, 2019 at 12:41 PM Gyan wrote:
> >> Ok. Then shouldn't it assign 'Sam John via ffmpeg-devel' as the author?
> >> It did do that for 'Oliver Collyer via ffmpeg-devel', the string w
On 18-04-2019 06:13 PM, Hendrik Leppkes wrote:
On Thu, Apr 18, 2019 at 12:41 PM Gyan wrote:
Ok. Then shouldn't it assign 'Sam John via ffmpeg-devel' as the author?
It did do that for 'Oliver Collyer via ffmpeg-devel', the string wrongly
substituted here.
This looks like a parser failure in P
On Thu, Apr 18, 2019 at 12:41 PM Gyan wrote:
>
>
>
> On 18-04-2019 03:25 PM, Timo Rothenpieler wrote:
> > On 18/04/2019 09:49, Gyan wrote:
> >>
> >> Patchwork can incorrectly assign ownership. See
> >> https://patchwork.ffmpeg.org/patch/12680/
> >>
> >> The author is Sam John as identified by Mess
Ok. Then shouldn't it assign 'Sam John via ffmpeg-devel' as the author?
It did do that for 'Oliver Collyer via ffmpeg-devel', the string wrongly
substituted here.
This looks like a parser failure in Patchwork.
Gyan
If the patch is sent with git send-email, the From: header of the E-Mail
is
On 18-04-2019 03:25 PM, Timo Rothenpieler wrote:
On 18/04/2019 09:49, Gyan wrote:
Patchwork can incorrectly assign ownership. See
https://patchwork.ffmpeg.org/patch/12680/
The author is Sam John as identified by Message ID as well as the
From field in the headers, yet Patchwork attributes
On 18/04/2019 09:49, Gyan wrote:
Patchwork can incorrectly assign ownership. See
https://patchwork.ffmpeg.org/patch/12680/
The author is Sam John as identified by Message ID as well as the From
field in the headers, yet Patchwork attributes this patch to "Oliver
Collyer via ffmpeg-devel", a
On Wed, Aug 24, 2016 at 01:16:05PM +0200, Michael Niedermayer wrote:
> Hi
>
> As i got a bit annoyed by accumulating duplicate and non applicable
> patches or rather the need to manually weed them out of patchwork
> ive yesterday quickly written the attached script
>
> Does something like this al
On Sun, Jul 31, 2016 at 01:39:15PM +0200, Michael Niedermayer wrote:
> Hi all
>
> raz has setup
> https://patchwork.ffmpeg.org
> feel free to register and use as you like
ill add every FFmpeg developer i spot amongth the registered users to
the maintainers of FFmpeg that way everyone can edit an
48 matches
Mail list logo
