[FFmpeg-devel] GitHub Integration

Soft Works softworkz at hotmail.com
Fri Jan 21 03:29:42 EET 2022



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of Soft Works
> Sent: Sunday, January 2, 2022 7:16 PM
> To: FFmpeg development discussions and patches <ffmpeg-devel at ffmpeg.org>
> Subject: Re: [FFmpeg-devel] GitHub Integration
> 
> 
> 
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of Lynne
> > Sent: Sunday, January 2, 2022 3:04 PM
> > To: FFmpeg development discussions and patches <ffmpeg-devel at ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] GitHub Integration
> >
> > 2 Jan 2022, 04:28 by softworkz at hotmail.com:
> >
> > >
> > >
> > >> -----Original Message-----
> > >> From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of Soft
> > Works
> > >> Sent: Tuesday, December 28, 2021 10:58 PM
> > >> To: FFmpeg development discussions and patches <ffmpeg-devel at ffmpeg.org>
> > >> Subject: Re: [FFmpeg-devel] GitHub Integration
> > >>
> > >> One component of the GitHub "Bridge" is a mirror of the ffmpeg-devel
> > >> mailing list as a Git repository which provides a web interfaces, can be
> > >> cloned via Git and can also be accessed from Atom feed readers.
> > >> This allows to follow the mailing list without subscribing. The web UI
> > >> might not be everybody's taste, though. It's the same that is used for
> > >> Linux kernel mailing lists (https://lore.kernel.org/git/).
> > >> I had to set this up as it's a requirement for the GitHub "Bridge", but
> > >> maybe it's useful for someone in other ways:
> > >>
> > >> https://master.gitmailbox.com/ffmpegdev/
> > >>
> > >
> > >
> > > I have just ACTIVATED patch submission via GitHub and submitted the first
> > > patch through this method.
> > >
> > > Pull requests can be created in this repository (for now):
> > >
> > > https://github.com/ffstaging/FFmpeg
> > >
> > >
> > > What's not nice is that the submitted e-mail shows "ffmpegagent" as
> sender
> > > and patchwork is showing it under that name as well.
> > >
> > > We'll need to see how this can be improved.
> > >
> >
> > I don't like it. Can't it use the author's name for emails?
> 
> I don't like this either. I'll try to find a way.


This is fixed now. See my patch from today:

[FFmpeg-devel] libavutil/tests/md5: Avoid warnings

Also, it appears correctly attributed on Patchwork:
(no longer as ffmpegagent)

https://patchwork.ffmpeg.org/project/ffmpeg/patch/pull.20.ffstaging.FFmpeg.1642727870274.ffmpegagent@gmail.com/

Regards,
softworkz





More information about the ffmpeg-devel mailing list