From: Adam Spiers <adam@spiers.net>
To: Zsh-workers@sunsite.auc.dk
Subject: Re: CVS ?
Date: Wed, 22 Mar 2000 16:56:11 +0000 [thread overview]
Message-ID: <20000322165611.A18419@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <1000322165019.ZM1475@candle.brasslantern.com>; from schaefer@candle.brasslantern.com on Wed, Mar 22, 2000 at 04:50:19PM +0000
Bart Schaefer (schaefer@candle.brasslantern.com) wrote:
> On Mar 22, 3:09pm, Ollivier Robert wrote:
> } Subject: CVS ?
> }
> } Is there any progress on the Sourceforge front ? Or has anyone started
> } their own CVS repository ?
>
> I thought Adam was waiting for a reply on whether sourceforge was willing
> to host the sources under the zsh license. Adam?
Still waiting :-( I'll give them another gentle poke now ...
> } Will there be snapshots again ?
>
> PWS has indicated he'll be starting up again soon. I sent him a list of
> the patches since -dev-19 (up through article 10168) a couple days ago.
>
> I'm now generally of the opinion that we should go ahead with sourceforge
> if they're OK with the license; initialize it by grabbing Tanaka's CVSROOT
> with cvsup and worry about the mailing lists later (probably, much later).
Except that his cvsupd stopped running a while ago, I think. Not that
that's a problem; I'm probably not the only one with a mirror of it.
> However, having waited this long, we might as well wait for PWS to give
> his opinion.
Agreed. He is the coordinator after all :-)
Adam -- very much looking forward to getting the latest code again
(haven't even got the wordcode stuff yet ...)
next prev parent reply other threads:[~2000-03-22 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-22 14:09 Ollivier Robert
2000-03-22 16:50 ` Bart Schaefer
2000-03-22 16:56 ` Adam Spiers [this message]
2000-03-24 10:46 ` Tanaka Akira
2000-03-22 23:22 ` 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=20000322165611.A18419@thelonious.new.ox.ac.uk \
--to=adam@spiers.net \
--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).