From: Chris Bagwell <chris@cnpbagwell.com>
To: sox-devel@lists.sourceforge.net
Subject: SoX Sourceforge Project Conversion
Date: Sat, 6 Apr 2013 12:49:09 -0500 [thread overview]
Message-ID: <CAGzDe_aX6ifWwxNfYi-tdsXaFku0KZ3MS+LVxNfskvPKL_Aw2Q@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 758 bytes --]
Hi all,
Sourceforge is changing the backend of all project to a new backend over
the next month or so... but projects can chose to upgrade earlier. I think
I will do this early upgrade next weekend (April 12th) so we have a little
more control over it. This is only 1 or so week early compared to April
22nd date Sourceforge team will start automatic conversions.
The main thing that will effect people that I've found (from other
project's conversion) is that the URL for our git repo will change. We
should be able to continue using our current cloned repos unaffected but
will have to issue a "git remote set-url origin ssh:..." to point to new
location.
If you prefer to be safe, you have the next week to push any changes you've
stored up.
Chris
[-- Attachment #1.2: Type: text/html, Size: 871 bytes --]
[-- Attachment #2: Type: text/plain, Size: 351 bytes --]
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
[-- 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
reply other threads:[~2013-04-06 21:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAGzDe_aX6ifWwxNfYi-tdsXaFku0KZ3MS+LVxNfskvPKL_Aw2Q@mail.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).