From: Adam Spiers <adam@spiers.net>
To: Zsh hackers list <zsh-workers@sunsite.auc.dk>
Subject: Re: updating development versions
Date: Mon, 3 Apr 2000 14:15:27 +0100 [thread overview]
Message-ID: <20000403141527.B32194@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <0FSF00MI9UT8JM@la-la.cambridgesiliconradio.com>; from pws@cambridgesiliconradio.com on Mon, Apr 03, 2000 at 12:34:20PM +0100
Peter Stephenson (pws@cambridgesiliconradio.com) wrote:
> - Adam set up a checked-out copy on sourceforge in
> /home/groups/zsh/zsh (the last zsh is the top-level CVS project
> directory). I have updated this, and configured it to install under
> /home/groups/zsh, so developers might want to use /home/groups/zsh/bin
> in their path.
Excellent, thanks. I was hoping someone would get around to that.
> I had to install yodl here to get it to work. This
> should provide us for the first time with a common platform for
> examining bugs, so it should be kept up to date by anyone using it. I
> suggest using `umask 002' here.
These files are all in group users, and writable by that group. Can I
suggest that you chgrp -R them to group zsh? I also did a chmod g+s
-R on /home/groups/zsh/zsh so that any new directories created would
end up in group zsh, so you might like to do that too.
> I haven't checked our quota; I don't
> know if we're going to run into difficulties doing this.
$ quota -g
Disk quotas for group users (gid 100): none
Disk quotas for group zsh (gid 5068):
Filesystem blocks quota limit grace files quota limit grace
/dev/sdb2 4535 102400 128000 737 3000 3500
> I still can't get into `change developer permissions'.
As I said elsewhere, I've submitted a bug report about this.
> Oliver, if you're interested in maintaining web pages, we could do
> with something basic on sourceforge, so if you want to register, Adam
> or I can add you as a developer.
Likewise, done.
> Links to the other zsh websites and
> to some zsh resources within sourceforge would be useful.
I already put a couple of links on http://zsh.sourceforge.net/, but this could doubtless be improved.
> though there's no reason why this shouldn't all be available at
> sunsite.auc.dk (some of it obviously already is).
I'm not keen with the way that www.zsh.org is more of a pointer than
the main webpage. Is there a good reason for this, and could it be
changed?
> I don't think there's any arrangement for CVS handling of web pages
> at sourceforge.
True, although I don't see any reason why we couldn't place htdocs
under the same repository as the source.
> I haven't even looked at the anon FTP stuff at sourceforge yet.
Nor me.
Adam
next prev parent reply other threads:[~2000-04-03 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-03 11:34 Peter Stephenson
2000-04-03 13:02 ` Geoff Wing
2000-04-03 13:25 ` Adam Spiers
2000-04-03 13:57 ` Geoff Wing
2000-04-03 13:15 ` Adam Spiers [this message]
2000-04-03 14:11 ` updating development versions and Re: bug in FAQ Oliver Kiddle
2000-04-03 18:41 ` Zefram
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=20000403141527.B32194@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).