zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Bruce Stephens" <bruce+zsh@cenderis.demon.co.uk>,
	"Bart Schaefer" <schaefer@candle.brasslantern.com>
Cc: <zsh-workers@sunsite.auc.dk>
Subject: RE: My public CVS repository will be closed.
Date: Tue, 29 Feb 2000 10:08:37 +0300	[thread overview]
Message-ID: <000001bf8283$ccb0f8e0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <87d7phcf11.fsf@cenderis.demon.co.uk>

>
> Why not <URL:http://sourceforge.net>?  Presuming they do what they say
> (and I've no reason to doubt them), they'll provide http, cvs, mailing
> lists, bug tracking and everything---and arrange for zsh.org to be
> redirected, if that's what we want.  All on good hardware.  (Obviously
> one can question whether this'll last for ever, but at the moment, it
> looks good.)
>

It even happened in my IE history :-)

Well, I think, you have mentioned it already less than a year ago. Now it
hosts quite a number of products/projects. Access is really good (via a
firewall in Germany in my case it is instant). Important thing is
ready-to-use CVS - normal and HTTP-based. All in all I agree - why not use
this one (keeping CVS repository backups 'course :-)

About lists - why not host them there. I nerver liked "real" domain in list
addresses - so, if we could finally arrange for

workers@zsh.org
users@zsh.org
...

so, that they could be transparently moved over, this would be really great.

The only thing, that bothers me - it is too good to be true :>

/andrej


      reply	other threads:[~2000-02-29  7:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-28 16:04 Tanaka Akira
2000-02-28 16:06 ` Ollivier Robert
2000-02-28 16:59   ` Bart Schaefer
2000-02-28 17:30     ` Tanaka Akira
2000-02-28 19:18     ` Bruce Stephens
2000-02-29  7:08       ` Andrej Borsenkow [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-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='000001bf8283$ccb0f8e0$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=bruce+zsh@cenderis.demon.co.uk \
    --cc=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).