From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] GitHub Integration
Date: Thu, 23 Dec 2021 14:08:54 +0000
Message-ID: <DM8P223MB0365BF97B824E673EF3C7347BA7E9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <fd10abfb4454bb13685c253c85ae02d7deb5e551.camel@acc.umu.se>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Tomas
> Härdin
> Sent: Thursday, December 23, 2021 3:00 PM
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] GitHub Integration
>
> ons 2021-12-22 klockan 23:24 +0000 skrev Soft Works:
> > Hi,
> >
> > holidays are approaching and I got a little present for all of you
> > even though it won’t be something for everybody.
> >
> > A while ago I had committed to prepare a test setup for integrating
> > GitHub in a similar way as the Git developers are doing.
> >
> > For those who missed it or don’t remember the outcome:
> > https://www.mail-archive.com/ffmpeg-devel@ffmpeg.org/msg123329.html
> > https://www.mail-archive.com/ffmpeg-devel@ffmpeg.org/msg123288.html
> >
> > Before someone’s temperature might start rising, I want to repeat
> > some important corner points:
> >
> > - it's not a migration nor the start of a migration
> > - nothing changes, it doesn't affect anybody's way of working
> > it doesn't replace anything
> > - it's an add-on that one could use or not
> >
> > Basic functionality is that it allows to submit patches to the ML
> > through GitHub pull requests.
>
> This sounds like something that will cause problems in the long run.
> Github will inevitably be brought into the project's workflow. People
> will start submitting tickets on Github rather than our trac. And so
> on.
Issues are disabled and hidden.
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:[~2021-12-23 14:25 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 [this message]
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
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=DM8P223MB0365BF97B824E673EF3C7347BA7E9@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