Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests
Date: Sun, 16 Feb 2025 19:55:38 +0200
Message-ID: <5858988.DvuYhMxLoT@basile.remlab.net> (raw)
In-Reply-To: <DM8P223MB0365623AD811781F078F3182BAFC2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>

Le torstaina 13. helmikuuta 2025, 1.07.25 UTC+2 Soft Works a écrit :
> > -----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'm afraid, but from my point of view, this doesn't match the objective.

Do you really expect to develop FFmpeg without using a CLI? In the first place, 
FFmpeg is a set of library and CLI tools.

As far as the Git CLI is concerned, I believe that the main objection is the 
reliance on git-send-email, and the implied need for an outbound SMTP server - 
not the need to use the Git GLI as such.

This should avoid both git-format-patch and git-send-email.

-- 
Rémi Denis-Courmont
Hagalund ny stad, f.d. Finska republik Nylands



_______________________________________________
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".

  parent reply	other threads:[~2025-02-16 17:55 UTC|newest]

Thread overview: 55+ 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-13 21:44                       ` Stephen Hutchinson
2025-02-14  2:13                         ` Timo Rothenpieler
2025-02-14  5:19                           ` Tanay Manerikar
2025-02-14  5:40                         ` Steven Liu
2025-02-12 22:12           ` Romain Beauxis
2025-02-12 23:22             ` Soft Works
2025-02-13 16:56             ` Romain Beauxis
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-16 17:58               ` Rémi Denis-Courmont
2025-02-16 19:20                 ` Soft Works
2025-02-17 13:46                   ` Rémi Denis-Courmont
2025-02-13 12:10             ` Tomas Härdin
2025-02-13 12:38               ` martin schitter
2025-02-16 17:55             ` Rémi Denis-Courmont [this message]
2025-02-16 18:59               ` Soft Works
2025-02-12 20:38   ` Michael Niedermayer
2025-02-19 22:02     ` Leandro Santiago

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=5858988.DvuYhMxLoT@basile.remlab.net \
    --to=remi@remlab.net \
    --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