Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 0/5] doc/developer: Add subsection about patch submission via FFstaging
Date: Fri, 9 May 2025 10:17:15 +0000
Message-ID: <DM8P223MB0365375C4743410F99C1BE4FBA8AA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <aByn37Au-CpdBCIs@phare.normalesup.org>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Nicolas
> George
> Sent: Donnerstag, 8. Mai 2025 14:47
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH 0/5] doc/developer: Add subsection about
> patch submission via FFstaging
> 
> Lynne (HE12025-05-08):
> > If its mentioned as part of our documentation, it's official.
> 
> I second your objection to this.
> 
> This proposal comes from softworkz, who has been here barely two
> minutes

For the record, if we consider the existence of FFmpeg as an hour,
like you are seeming to allude to and look at the first commit as
evidence for being here, then we get to the following results:

+-----------+--------+
| Fabrice   | 60 min |
+-----------+--------+
| Michael   | 58 min |
+-----------+--------+
| Nicolas   | 44 min |
+-----------+--------+
| James     | 32 min |
+-----------+--------+
| softworkz | 22 min |
+-----------+--------+
| Andreas   | 16 min |
+-----------+--------+
| Lynne     | 15 min |
+-----------+--------+

It obviously doesn't say anything about the amount of contribution,
but well - it was _your_ analogy.

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

  parent reply	other threads:[~2025-05-09 10:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08 10:22 ffmpegagent
2025-05-08 10:22 ` [FFmpeg-devel] [PATCH 1/5] doc/developer: Move checklist into Submitting Patches chapter softworkz
2025-05-08 10:22 ` [FFmpeg-devel] [PATCH 2/5] doc/developer: Move codecs/formats checklist into Development Policy chapter softworkz
2025-05-08 10:22 ` [FFmpeg-devel] [PATCH 3/5] doc/developer: Reorder Submission procedures content softworkz
2025-05-08 10:22 ` [FFmpeg-devel] [PATCH 4/5] doc/developer: Merge Review paragraphs and deduplicate softworkz
2025-05-08 10:22 ` [FFmpeg-devel] [PATCH 5/5] doc/developer: Add subsection about patch submission via FFstaging softworkz
2025-05-08 12:40   ` James Almer
2025-05-08 12:55     ` softworkz .
2025-05-08 11:13 ` [FFmpeg-devel] [PATCH 0/5] " softworkz .
2025-05-08 11:20 ` Lynne
2025-05-08 11:33   ` softworkz .
2025-05-08 11:59     ` Lynne
2025-05-08 12:26       ` softworkz .
2025-05-08 12:36         ` Lynne
2025-05-08 12:47           ` Nicolas George
2025-05-08 13:12             ` softworkz .
2025-05-09 10:17             ` softworkz . [this message]
2025-05-13 18:05 ` [FFmpeg-devel] [PATCH v2 0/4] doc/developer: Restructure docs about patch submission ffmpegagent
2025-05-13 18:05   ` [FFmpeg-devel] [PATCH v2 1/4] doc/developer: Move checklist into Submitting Patches chapter softworkz
2025-05-13 18:05   ` [FFmpeg-devel] [PATCH v2 2/4] doc/developer: Move codecs/formats checklist into Development Policy chapter softworkz
2025-05-13 18:05   ` [FFmpeg-devel] [PATCH v2 3/4] doc/developer: Reorder Submission procedures content softworkz
2025-05-13 18:05   ` [FFmpeg-devel] [PATCH v2 4/4] doc/developer: Merge Review paragraphs and deduplicate softworkz

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=DM8P223MB0365375C4743410F99C1BE4FBA8AA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz-at-hotmail.com@ffmpeg.org \
    --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