From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Clint Adams" <schizo@debian.org>, <zsh-workers@sunsite.auc.dk>
Subject: RE: CVS again (Re: Module idea to help developers)
Date: Fri, 15 Oct 1999 18:08:29 +0400 [thread overview]
Message-ID: <000e01bf1716$c1c07c40$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <19991015095712.C16453@dman.com>
>
> > I have access to a well-specced and reliable RedHat box with a
> > high-bandwidth connection in the UK, use of which as a temporary
> > zsh-workers CVS facility would be welcome. Then when the Sunsite
> > people re-emerge, it could be moved there if so desired.
>
> Since this doesn't seem to be going anywhere..
> Maybe you could start by maintaining a unofficial anonymous read-only
> repository so people can get a "current" snapshot.
>
For this to work we need
... somebody, who will collect patches and keep CVS in sync
or (better yet)
... the key ZSH developers should have write access to repository and do direct
updates there. There is no point in sending patches to list then. Some
announcement/notification is still welcome - e.g. SAMBA has CVS list with commit
messages. But setting up yet another list needs cooperation form Sunsite as well
... sigh.
I opt for the latter. We just need some common framework (branches/tag names
etc). And commit messages may probably go to the zsh-workers (with some special
subject. I believe, it can be setup in CVS).
/andrej
next prev parent reply other threads:[~1999-10-15 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-13 16:20 Module idea to help developers Bart Schaefer
1999-10-13 18:42 ` Clint Adams
1999-10-14 3:48 ` Bart Schaefer
1999-10-14 10:52 ` Oliver Kiddle
1999-10-14 12:27 ` CVS again (Re: Module idea to help developers) Adam Spiers
1999-10-15 13:57 ` Clint Adams
1999-10-15 14:08 ` Andrej Borsenkow [this message]
1999-10-15 14:19 ` 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='000e01bf1716$c1c07c40$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=schizo@debian.org \
--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).