From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] GitHub Integration
Date: Sun, 2 Jan 2022 18:16:22 +0000
Message-ID: <DM8P223MB0365FDFF5920029BBDA60776BA489@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <MsQ5k7h--3-2@lynne.ee>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Lynne
> Sent: Sunday, January 2, 2022 3:04 PM
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] GitHub Integration
>
> 2 Jan 2022, 04:28 by softworkz@hotmail.com:
>
> >
> >
> >> -----Original Message-----
> >> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Soft
> Works
> >> Sent: Tuesday, December 28, 2021 10:58 PM
> >> To: FFmpeg development discussions and patches <ffmpeg-devel@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.
sw
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-01-02 18:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 23:24 Soft Works
2021-12-23 7:35 ` Paul B Mahol
2021-12-23 8:10 ` Soft Works
2021-12-23 13:59 ` Tomas Härdin
2021-12-23 14:08 ` Soft Works
2021-12-23 14:16 ` Timo Rothenpieler
2021-12-23 20:50 ` Soft Works
2021-12-23 22:30 ` Soft Works
2021-12-25 9:31 ` Vasily
2021-12-25 9:33 ` Vasily
2021-12-25 11:12 ` Michael Niedermayer
2021-12-25 16:27 ` Soft Works
2021-12-25 16:23 ` Soft Works
2021-12-25 16:50 ` Lynne
2021-12-25 17:15 ` Soft Works
2021-12-26 0:54 ` lance.lmwang
2021-12-26 1:03 ` Steven Liu
2021-12-26 16:48 ` Lynne
2021-12-26 20:21 ` Soft Works
2021-12-26 21:37 ` Ronald S. Bultje
2021-12-26 23:10 ` Soft Works
2021-12-27 1:41 ` lance.lmwang
2021-12-27 14:59 ` Zane van Iperen
2021-12-27 15:36 ` Vasily
2021-12-28 21:21 ` Niklas Haas
2021-12-28 21:57 ` Soft Works
2022-01-02 3:28 ` Soft Works
2022-01-02 14:04 ` Lynne
2022-01-02 18:16 ` Soft Works [this message]
2022-01-21 1:29 ` Soft Works
2021-12-29 19:57 ` Anton Khirnov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM8P223MB0365FDFF5920029BBDA60776BA489@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz@hotmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git