From: Jan Stary <hans@stare.cz>
To: sox-devel@lists.sourceforge.net
Cc: sox-users@lists.sourceforge.net
Subject: Re: Post to sox-devel@public-inbox.org denied: Re: [SoX-users] how to interpret tell_off, and the right way to use sox_seek
Date: Tue, 7 Nov 2017 21:41:07 +0100 [thread overview]
Message-ID: <20171107204107.GA42875@www.stare.cz> (raw)
In-Reply-To: <20171107181423.GA23185@dcvr>
On Nov 07 18:14:23, normalperson@yhbt.net wrote:
> Jan Stary <hans@stare.cz> wrote:
> > Sorry for crossposting, but whoever's running the public-inbox.org mirror,
> > please get it fixed.
>
> Sorry, though I'm not sure what's tripping up mlmmj for you.
> I'll disable mlmmj for this list since it wasn't used anyways...
>
> Was that the only bounce you've seen, lately?
Yes.
But I have inly been posting to sox-users lately,
this was the inly post to sox-devel.
> But the HTTPS mirrors at https://public-inbox.org/sox-devel/ should
> remain up.
The mirror at
https://marc.info/?l=sox-users&r=1&w=2
https://marc.info/?l=sox-devel&r=1&w=2
is very reliable and the interface sucks way less.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
next prev parent reply other threads:[~2017-11-07 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1510049155-26818-mlmmj-0860bf8a@public-inbox.org>
2017-11-07 15:12 ` Post to sox-devel@public-inbox.org denied: Re: [SoX-users] how to interpret tell_off, and the right way to use sox_seek Jan Stary
2017-11-07 18:14 ` Eric Wong
2017-11-07 20:41 ` Jan Stary [this message]
2017-11-08 0:47 ` Eric Wong
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=20171107204107.GA42875@www.stare.cz \
--to=sox-devel@lists.sourceforge.net \
--cc=sox-users@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).