zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: sourceforge.net CVS tree ready for use
Date: Sat, 01 Apr 2000 21:51:24 +0100	[thread overview]
Message-ID: <E12bUrd-0002V3-00.2000-04-01-21-51-26@cmailg5.svr.pol.co.uk> (raw)
In-Reply-To: "Adam Spiers"'s message of "Sat, 01 Apr 2000 12:11:50 BST." <20000401121150.A18158@thelonious.new.ox.ac.uk>

Adam Spiers wrote:
> The CVS repository at sourceforge.net has been prepared from a recent
> (everything up to 10250, I believe) copy of Tanaka's repository, and
> is now ready for use.

Excellent, thank you very much.  I have added all the changes up to date,
namely my patch for LICENCE.  (Do you want `make prep' to copy that to
LICENSE? :-/) So the usual suspects are welcome to commit their own
changes.

One question is whether we commit CVS changes straight away, i.e. when the
patch is posted to the list, or wait for comments.  The latter will be a
little messy, since other developers would have to apply the patch to try
it, then remove it to avoid CVS reporting a conflict.  So I think with
non-contentious patches we might as well do it simultaneously.

We should certainly think about Andrej's suggestion that the patches can be
moved offlist now we have a regular repository.  As we have write
permission on sourceforge, a way for doing that over the net could probably
be handled.  Or maybe Geoff can think of something he can set up.

Some time, probably tomorrow since I'm zsh'd out, I shall
 - finalise 3.1.6-dev-21 and put it in the usual place, too
 - post an announcement to zsh-announce about the availablity of the CVS
   archive at sourceforge
 - all the other stuff I've forgotten to do which you're going to
   remind me.

-- 
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
Work: pws@CambridgeSiliconRadio.com
Web: http://www.pwstephenson.fsnet.co.uk


  reply	other threads:[~2000-04-01 20:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-26  0:50 zsh license preventing move to sourceforge.net? (fwd) Adam Spiers
2000-03-26 19:06 ` Clint Adams
2000-03-26 22:19 ` Peter Stephenson
2000-03-28  0:28   ` move to sourceforge.net in progress Adam Spiers
2000-03-27 21:24     ` Peter Stephenson
2000-04-01 11:11       ` sourceforge.net CVS tree ready for use Adam Spiers
2000-04-01 20:51         ` Peter Stephenson [this message]
2000-04-02  0:44           ` Bart Schaefer
2000-04-02  0:45           ` Adam Spiers
2000-04-02  4:37             ` Bart Schaefer
2000-04-02  6:02               ` Geoff Wing
2000-04-02 22:02                 ` Adam Spiers
2000-04-02 23:16                   ` Bart Schaefer
2000-04-02 10:10         ` Andrej Borsenkow
2000-04-02 10:35           ` Geoff Wing
2000-04-02 23:29             ` Bart Schaefer
2000-04-03  8:50               ` Geoff Wing
2000-04-03 10:30         ` Oliver Kiddle
2000-04-03 13:06           ` Adam Spiers
2000-03-28  1:46     ` move to sourceforge.net in progress Bart Schaefer
2000-03-28 11:45     ` Andrej Borsenkow
2000-03-28 16:51       ` Bart Schaefer
2000-04-02 14:06 sourceforge.net CVS tree ready for use dmeyer

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=E12bUrd-0002V3-00.2000-04-01-21-51-26@cmailg5.svr.pol.co.uk \
    --to=pws@pwstephenson.fsnet.co.uk \
    --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).