From: Martin Guy <martinwguy@gmail.com>
To: sox-devel@lists.sourceforge.net
Subject: Fwd: Offering to step up as new SoX maintainer
Date: Thu, 6 Jun 2024 13:07:37 +0200 [thread overview]
Message-ID: <303b1197-d6ee-4173-ac89-79a8e07cc253@gmail.com> (raw)
In-Reply-To: <ZmGXAG4DGfqNG4qo@www.stare.cz>
[-- Attachment #1.1.1: Type: text/plain, Size: 739 bytes --]
I had to forward this to the list. It had me laughing in my throne.
-------- Forwarded Message --------
Subject: Re: [SoX-devel] Offering to step up as new SoX maintainer
Date: Thu, 6 Jun 2024 13:01:20 +0200
From: Jan Stary <hans@stare.cz>
To: Martin Guy <martinwguy@gmail.com>
> > > > The rule for modifying existing codebases is to respect and follow the
> > > > existing coding styles.
> >
> > Bullshit. With that attitude,
> > we would still be stuck with OpenSSL.
>
> Sorry, that one went over my head. OpenSSL? Did it have bad indentation or
> layout? I think I missed something there
Yes, apparently:
https://www.openbsd.org/papers/bsdcan14-libressl/
----------------------------------
:D :D :D
M
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 158 bytes --]
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
parent reply other threads:[~2024-06-06 11:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <ZmGXAG4DGfqNG4qo@www.stare.cz>]
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=303b1197-d6ee-4173-ac89-79a8e07cc253@gmail.com \
--to=sox-devel@lists.sourceforge.net \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).