From: Jan Stary <hans@stare.cz>
To: sox-devel@lists.sourceforge.net, sox-users@lists.sourceforge.net
Subject: Re: [SoX-devel] New SoX git repos
Date: Wed, 4 Sep 2013 08:23:44 +0200 [thread overview]
Message-ID: <20130904062343.GA30671@www.stare.cz> (raw)
In-Reply-To: <CAGzDe_Ym3EAL_bL1V1DcdZdFZ4_nP2kB1=2=JCXy99R+0ED9dw@mail.gmail.com>
On Apr 14 10:48:23, chris@cnpbagwell.com wrote:
> The SoX project has been moved to a new Sourceforge backend which means the
> URL for the git repository has changed.
>
> Warning: the old one still exists and is a read-only copy that will not be
> updated. Please be aware you will get no failure messages when doing "git
> pull" on your old clone's.
>
> If you wish to track SoX updates using a local clone or if your a
> developer, you will need to re-clone or update the URL for your existing
> clone.
>
> The new git web interface is located here; which includes the new repo URL
> you will need to use:
>
> http://sourceforge.net/p/sox/code/ci/master/tree/
>
> You can update your existing clone by issuing one of these two commands.
>
> Read-only clones:
> git remote set-url origin git://git.code.sf.net/p/sox/code
The homepage sox.sf.net still says
git clone git://sox.git.sourceforge.net/gitroot/sox/sox
- is that intended?
Jan
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
prev parent reply other threads:[~2013-09-04 6:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-14 15:48 New SoX git repos Chris Bagwell
2013-09-04 6:23 ` Jan Stary [this message]
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=20130904062343.GA30671@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).