zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Adam Spiers <adam@spiers.net>,
	zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: move to sourceforge.net?
Date: Fri, 10 Mar 2000 16:58:52 +0000	[thread overview]
Message-ID: <1000310165852.ZM18878@candle.brasslantern.com> (raw)
In-Reply-To: <20000310163259.A2867@thelonious.new.ox.ac.uk>

On Mar 10,  4:32pm, Adam Spiers wrote:
} Subject: move to sourceforge.net?
}
} Are there any objections to this move, and if not, would I be helping
} or just getting in the way by registering zsh as a project on
} sourceforge?

You can answer some questions about sourceforge that I haven't had a
chance to investigate yet: 

Can the repository be made read-only except by some limited group of
administrators?

Can we copy over Tanaka's existing repository in its entirety, without
losing any of the change history?  (I hope it's still available with
cvsupd or whatever that's called; but I don't know what that's capable
of exporting nor what sourceforge is capable of importing.)

Can we set up any of our own patch management tools, e.g. Tanaka's
scripts for applying patches from the mailing list and then running
"cvs import"?

If not, do they have an equivalent?  (Patch Manager doesn't sound like
it has that as a function, from a quick look at that press release.)

If there is nothing of the kind, what do the administrators have to do?

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  parent reply	other threads:[~2000-03-10 16:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-10 16:32 Adam Spiers
2000-03-10 16:40 ` Adam Spiers
2000-03-10 16:56 ` Oliver Kiddle
2000-03-10 16:58 ` Bart Schaefer [this message]
2000-03-10 18:51   ` Adam Spiers
2000-03-17 16:23     ` Brian Boonstra
2000-03-10 19:42   ` Bruce Stephens

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=1000310165852.ZM18878@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=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).