From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests
Date: Thu, 13 Feb 2025 13:10:03 +0100
Message-ID: <75e9f7ca048022e2fb2a289b4a1b09b58ab0c98f.camel@haerdin.se> (raw)
In-Reply-To: <DM8P223MB0365623AD811781F078F3182BAFC2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
ons 2025-02-12 klockan 23:07 +0000 skrev Soft Works:
>
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> > Timo
> > Rothenpieler
> > Sent: Mittwoch, 12. Februar 2025 22:33
> > To: ffmpeg-devel@ffmpeg.org
> > Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull
> > requests
> >
> > On 12.02.2025 22:22, Stephen Hutchinson wrote:
> > > Are all accounts restricted to owning a maximum of 0 repositories
> > > by
> > > default, or is it set to 0 only for those that sign up through
> > > one of
> > > the external logins?
> >
> > It's set to 0 by default, to avoid spammers uploading junk, or just
> > people (ab)using it for non-ffmpeg things.
> >
> > You can open issues and comment on existing PRs.
> > And also create PRs using the AGit workflow:
> > https://forgejo.org/docs/latest/user/agit-support/
>
> For those who are too lazy to look it up:
>
> The "Agit workflow" requires you to use non-standard Git "push-
> options"
> (either -o or --push-options):
>
> git push origin HEAD:refs/for/master -o topic="topic-branch" \
> -o title="Title of the PR" \
> -o description="# The PR Description
> This can be **any** markdown content.\n
> - [x] Ok"
>
> This means essentially that our attempt to move away from the e-mail-
> based submission procedure to something easy and user-friendly, would
> end up in replacing the current rarely-known mechanism with another
> even more rare and obscure procedure which would (again) force
> everybody to use the Git command line because it's (again) not
> supported by any tooling except Git CLI.
I see this as a plus. More stuff should be done with git alone. This is
one case where fossil shines, because it combines code, tickets and
wiki into one single CLI tool.
/Tomas
_______________________________________________
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:[~2025-02-13 12:10 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 18:06 Michael Niedermayer
2025-02-12 18:49 ` Lynne
2025-02-12 18:53 ` Romain Beauxis
2025-02-12 19:23 ` Lynne
2025-02-12 21:22 ` Stephen Hutchinson
2025-02-12 21:32 ` Timo Rothenpieler
2025-02-12 21:37 ` Soft Works
2025-02-12 21:51 ` Timo Rothenpieler
2025-02-12 22:01 ` Soft Works
2025-02-12 22:05 ` Timo Rothenpieler
2025-02-12 22:16 ` Soft Works
2025-02-12 23:29 ` Timo Rothenpieler
2025-02-12 23:34 ` Kieran Kunhya via ffmpeg-devel
2025-02-13 0:27 ` Timo Rothenpieler
2025-02-13 12:07 ` Tomas Härdin
2025-02-13 4:05 ` martin schitter
2025-02-13 8:49 ` Leo Izen
2025-02-13 9:27 ` Tanay Manerikar
2025-02-13 12:40 ` Leo Izen
2025-02-13 9:49 ` Gyan Doshi
2025-02-13 10:30 ` Soft Works
2025-02-13 12:37 ` Leo Izen
2025-02-13 13:32 ` Timo Rothenpieler
2025-02-12 22:12 ` Romain Beauxis
2025-02-12 23:22 ` Soft Works
2025-02-12 23:07 ` Soft Works
2025-02-12 23:34 ` Timo Rothenpieler
2025-02-13 0:17 ` Soft Works
2025-02-13 0:24 ` Romain Beauxis
2025-02-13 0:40 ` Soft Works
2025-02-13 1:52 ` Timo Rothenpieler
2025-02-13 2:59 ` Soft Works
2025-02-13 6:14 ` Lynne
2025-02-13 6:50 ` martin schitter
2025-02-13 6:54 ` Soft Works
2025-02-13 7:24 ` Soft Works
2025-02-13 13:32 ` Timo Rothenpieler
2025-02-13 11:04 ` Tobias Rapp
2025-02-13 12:07 ` Soft Works
2025-02-13 12:27 ` Soft Works
2025-02-13 13:37 ` Timo Rothenpieler
2025-02-13 12:10 ` Tomas Härdin [this message]
2025-02-13 12:38 ` martin schitter
2025-02-12 20:38 ` Michael Niedermayer
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=75e9f7ca048022e2fb2a289b4a1b09b58ab0c98f.camel@haerdin.se \
--to=git@haerdin.se \
--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