From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: CVS problems at SourceForge
Date: Wed, 25 Jun 2003 16:16:33 +0000 [thread overview]
Message-ID: <1030625161634.ZM9928@candle.brasslantern.com> (raw)
In-Reply-To: <23043.1056552034@gmcs3.local>
On Jun 25, 4:40pm, Oliver Kiddle wrote:
} Subject: Re: CVS problems at SourceForge
}
} It is probably worth reading what they say at:
} http://sourceforge.net/docman/display_doc.php?docid=2352&group_id=1#cvs
I did read it ... that was the reason behind starting this thread.
(I wouldn't have forwarded that SA-list message without checking on
the information it referenced.)
} Are you using the pserver for any reason other than to save yourself the
} hassle of typing your password/ssh passphrase?
I use "cvs login" from my home machine where I have my working sandbox
(the one where I do what little zsh dev work I squeeze in these days).
I use the pserver at work for installing zsh, because I never want to
commit any local changes I may make there.
Not everyone is a zsh developer with login access to the sources, though.
} If we move we should make sure that the alternative even offers
} anonymous CVS access. I'd also be reluctant to loose the daily snapshots
} and ability to download the repository tarball.
Yes. I'd rather not have to move, either, but if sourceforge is going
to collapse into a black hole under the weight of its own success ...
} Also if we move, it'd be worth reconsidering other things like how we
} use the bug tracker
Which at the moment we don't, really ... I suppose somebody is monitoring
it, but this list is still the real "bug tracker" for zsh.
next prev parent reply other threads:[~2003-06-25 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-14 23:09 Bart Schaefer
2003-06-15 1:25 ` Dan Nelson
2003-06-24 9:29 ` Oliver Kiddle
2003-06-24 17:35 ` Bart Schaefer
2003-06-25 14:40 ` Oliver Kiddle
2003-06-25 16:16 ` Bart Schaefer [this message]
2003-06-25 13:16 ` Clint Adams
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=1030625161634.ZM9928@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.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).