From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: Zsh Hackers' List <zsh-workers@zsh.org>
Subject: Re: Fw: zsh, it's time to upgrade your classic SourceForge project
Date: Tue, 15 Jan 2013 18:58:29 -0500 [thread overview]
Message-ID: <20130115235829.GA29548@redoubt.spodhuis.org> (raw)
In-Reply-To: <20130115194529.6855de7d@pws-pc.ntlworld.com>
On 2013-01-15 at 19:45 +0000, Peter Stephenson wrote:
> Sourceforge is updating their system; for some reason this time round
> it's not automatic. I shall probably just press the button, but beware
> the URLs will changed (it's not as if that would be the first time).
> Now is probably as good a time as any.
<https://sourceforge.net/p/upgrade/> just gives an error message about
not being an admin of "this" project.
Looking around to try to find documentation on what changes, I find:
https://sourceforge.net/p/forge/site-support/537/
where SF's support point out that CVS URLs will *not* change:
----------------------------8< cut here >8------------------------------
CVS is actually a special case. We don't support it for new projects on
the new system, only for classic projects that upgrade. So that said,
the repository itself isn't actually migrated, it's just left in place
and we add an informational page similar to what's on classic projects.
So, in short, yes, for CVS (and only CVS), the links will remain the
same.
----------------------------8< cut here >8------------------------------
So, looks like no manual fixups of client checkouts needed.
-Phil
next prev parent reply other threads:[~2013-01-16 0:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 19:45 Peter Stephenson
2013-01-15 23:58 ` Phil Pennock [this message]
2013-01-17 19:55 ` Peter Stephenson
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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130115235829.GA29548@redoubt.spodhuis.org \
--to=zsh-workers+phil.pennock@spodhuis.org \
--cc=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@zsh.org \
/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://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).