Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] Posting correctly (was: Accept a colon in the path of a URI, instead of stripping preceding characters.)
Date: Wed, 21 May 2025 21:14:58 +0200
Message-ID: <aC4mMsdZiQmIZTpo@phare.normalesup.org> (raw)
In-Reply-To: <DM8P223MB0365F0A14F3321B4DB086145BA9EA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>

softworkz . (HE12025-05-21):
> From: Timothy Allen <tim@treehouse.org.za>
> Sent: Mittwoch, 21. Mai 2025 09:29
> To: softworkz . <softworkz@hotmail.com>; FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] Accept a colon in the path of a URI, instead of stripping preceding characters.
> 
> On Tue, 2025-05-20 at 20:03 +0000, softworkz . wrote:
> I was just about to reply and suggest to replace those colons with %3A
> (url-encoded) when I read the ticket, which already suggests that.
<snip>

Your message is absolutely unreadable. It is not my software that makes
it so, it is unreadable on the official archive as well:

https://ffmpeg.org/pipermail/ffmpeg-devel/2025-May/343902.html

Compare with the message you are responding to:

https://ffmpeg.org/pipermail/ffmpeg-devel/2025-May/343841.html

It is impossible to know which parts you wrote and which parts you
quote, let alone distinguish quotes from double quotes.

Before you allow yourself to badmouth the tool mailing again, you need
to make the minimum amount of effort to use it properly. If not for
yourself, at least out of basic respects for the other people who use
it. That means making sure your mails are at least as readable as the
ones from other experienced developers. You can observe them rendered in
the archive, not mangled by your local mail software. Start with having
a real attribution instead of that awful blob of headers.

And if that makes you realize the software you have been using is crap
and change it, so much the better, and then realize that with proper
software a mailing-list is an excellent tool, so much the better. But I
will not hold my breath.

-- 
  Nicolas George
_______________________________________________
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-21 19:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20 15:27 [FFmpeg-devel] [PATCH] Accept a colon in the path of a URI, instead of stripping preceding characters Timothy Allen via ffmpeg-devel
2025-05-20 19:49 ` Marton Balint
2025-05-20 20:03 ` softworkz .
2025-05-21  7:28   ` Timothy Allen via ffmpeg-devel
2025-05-21 18:56     ` softworkz .
2025-05-21 19:09       ` Timothy Allen via ffmpeg-devel
2025-05-21 19:25         ` softworkz .
2025-05-21 20:04           ` Timothy Allen via ffmpeg-devel
2025-05-21 19:14       ` Nicolas George [this message]

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=aC4mMsdZiQmIZTpo@phare.normalesup.org \
    --to=george@nsup.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