unofficial mirror
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: Re: better sndio support in SoX
Date: Wed, 21 Sep 2016 06:58:52 +0000	[thread overview]
Message-ID: <20160921065852.GA18155@starla> (raw)
In-Reply-To: <>

Jan Stary <> wrote:
> On Sep 20 22:24:28, wrote:
> > Thanks, it's sitting in my "pu" branch on git://
> > with Alex credited as the author.
> Thank you.
> What is the relation of this git branch at git://
> to the actual SoX repository at git:// ?

Just another git repository.  I don't have rights on SF,
nor do I much care for the URL[*]

And I believe git URLs should be treated equally (so I reject
the Embrace, Extend, ... concept of git hosts which add
proprietary features to git).

I'm just keeping my git repo on git:// up-to-date
so Chris et al. can more easily resume maintenance someday
without having to dig through bug tracker + archives.

[*] Except makes the usability mistake of having
   "code" as the basename, making the user type more when
    cloning (or end up with a directory named "code").
    Back in the day, made a similar mistake,
    which I think hurt their adoption.

> > commit ea4f3fb3c6de93e10786fbfc1cb1bdf9006bbcdb
> > Author: Alexandre Ratchov <>
> > Date:   Tue Sep 20 22:00:40 2016 +0000
> > 
> >     sndio: handle 24-bit samples properly on OpenBSD
> That's a bit misleading: it will properly handle
> whatever bitwidth SoX asks for. The 24 vs 32 was
> just the initiating problem.

Oops.  Can you propose a standalone commit message which
I can copy and use directly?  Thanks.

(I much prefer commit messages written with the patch
 submission itself, basically, same conventions as
 Linux kernel and git.git development).


  reply	other threads:[~2016-09-21  6:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15 11:29 better sndio support in SoX Jan Stary
2016-09-20 19:39 ` Eric Wong
2016-09-20 20:06   ` Måns Rullgård
2016-09-20 21:36   ` Jan Stary
2016-09-20 22:24     ` Eric Wong
2016-09-21  5:45       ` Jan Stary
2016-09-21  6:58         ` Eric Wong [this message]
2016-09-21  7:19           ` Jan Stary
2016-09-21 11:42             ` Alexandre Ratchov
2016-09-21 11:19         ` Måns Rullgård
2016-09-21 11:42           ` Alexandre Ratchov

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160921065852.GA18155@starla \ \

* 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

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