unofficial mirror
 help / color / mirror / code / Atom feed
From: "Måns Rullgård" <>
Subject: Re: upstream
Date: Sun, 18 Mar 2018 14:56:31 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Jan Stary's message of "Sat, 17 Mar 2018 15:40:21 +0100")

Jan Stary <> writes:

> Hi all,
> what is the upstream of SoX nowadays?
> I use git://
> which head its last commit three years ago.
> says 
> Brought to you by: cbagwell, robs, uklauer
> Is any of you guys around here, and still active in maintaining SoX?
> My impression is that Mans and Pascal are mostly the maintainers now
> - do you have commit rights to toe SF repo?

I have no rights to the SF repo.

> Is that the right repo?

Define right.

> Do you maintain your fork elsewhere?

I maintain my fork at

> What is tha right place to send PRs?
> Is thete a point opening tickets on SF?

Probably not.  If you open issues on my github repo, I'll at least see
them.  Maybe I'll even fix them.

Måns Rullgård

Check out the vibrant tech community on one of the world's most
engaging tech sites,!
SoX-devel mailing list

  reply	other threads:[~2018-03-18 14:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-17 14:40 upstream Jan Stary
2018-03-18 14:56 ` Måns Rullgård [this message]
2018-03-18 19:41   ` upstream Eric Wong
2018-03-19 11:31     ` upstream Måns Rullgård
2018-03-18 20:50 ` upstream Jan Stary
2018-03-18 22:05   ` upstream Eric Wong
2018-03-19 20:19     ` upstream Rob Sykes via SoX-devel
2018-04-25  8:03       ` upstream Eric Wong
2018-04-25  9:55         ` upstream Måns Rullgård
2018-04-26 10:27           ` upstream Rob Sykes via SoX-devel
2018-03-19 11:41   ` upstream Måns Rullgård
2018-03-22  2:21   ` upstream Jan Stary
2018-03-22 16:37     ` upstream Sonny Ray

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 \ \ \ \

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