Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] QOA decoding support
Date: Fri, 6 Oct 2023 13:54:47 +0200
Message-ID: <CAPYw7P6=PLFYc9tf-VL4qub+puZUdM+LTQvVwD_s0tftw=o2SQ@mail.gmail.com> (raw)
In-Reply-To: <CAPYw7P4VtuVZvdhWZBk-oMWfQFX6cf_PYbZcw-Vg4wn1zSm9Cg@mail.gmail.com>

On 9/27/23, Paul B Mahol <onemda@gmail.com> wrote:
> On 9/27/23, Michael Niedermayer <michael@niedermayer.cc> wrote:
>> On Wed, Sep 27, 2023 at 03:00:35PM +0200, Paul B Mahol wrote:
>>> On Wed, Sep 27, 2023 at 2:57 PM Nicolas George <george@nsup.org> wrote:
>>>
>>> > Paul B Mahol (12023-09-27):
>>> > > I think that having parser is much more useful.
>>> >
>>> > Having a parser when it can be done without is a waste of code and
>>> > resources.
>>> >
>>> > Do not push like that.
>>> >
>>>
>>> As you never pushed anything marginally useful to codebase, I'm free to
>>
>> 6 Code of Conduct
>> Be friendly and respectful towards others and third parties. Treat others
>> the way you yourself want to be treated.
>> Be considerate. Not everyone shares the same viewpoint and priorities as
>> you
>> do. Different opinions and interpretations help the project. Looking at
>> issues from a different perspective assists development.
>> Do not assume malice for things that can be attributed to incompetence.
>> Even
>> if it is malice, it’s rarely good to start with that as initial
>> assumption.
>> Stay friendly even if someone acts contrarily. Everyone has a bad day
>> once
>> in a while. If you yourself have a bad day or are angry then try to take
>> a
>> break and reply once you are calm and without anger if you have to.
>> Try to help other team members and cooperate if you can.
>> The goal of software development is to create technical excellence, not
>> for
>> any individual to be better and "win" against the others. Large software
>> projects are only possible and successful through teamwork.
>> If someone struggles do not put them down. Give them a helping hand
>> instead
>> and point them in the right direction.
>> Finally, keep in mind the immortal words of Bill and Ted, "Be excellent
>> to
>> each other."
>>
>> Thank you
>
> Thanks, will push patch set in next 12h.
>

Oh, forgot to push, pushing soon.
_______________________________________________
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".

  reply	other threads:[~2023-10-06 11:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-23 21:39 Paul B Mahol
2023-09-24  0:05 ` Andreas Rheinhardt
2023-09-24  0:48   ` Paul B Mahol
2023-09-27 12:52     ` Andreas Rheinhardt
2023-09-27 12:52       ` Paul B Mahol
2023-09-27 12:57         ` Nicolas George
2023-09-27 13:00           ` Paul B Mahol
2023-09-27 18:37             ` Michael Niedermayer
2023-09-27 19:59               ` Paul B Mahol
2023-10-06 11:54                 ` Paul B Mahol [this message]
2023-09-27 13:02           ` Paul B Mahol
2023-09-27 12:58       ` Nicolas George
2023-09-27 13:05         ` Andreas Rheinhardt
2023-09-27 13:09           ` Paul B Mahol
2023-09-24  0:50 ` Paul B Mahol
2023-09-27 12:44   ` Paul B Mahol
2023-09-27 12:54   ` Tomas Härdin
2023-09-27 12:56     ` Paul B Mahol
2023-09-27 12:57       ` Tomas Härdin
2023-09-27 12:59         ` Paul B Mahol
2023-09-27 13:05           ` Tomas Härdin

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='CAPYw7P6=PLFYc9tf-VL4qub+puZUdM+LTQvVwD_s0tftw=o2SQ@mail.gmail.com' \
    --to=onemda@gmail.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