From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] proposal: a patch acceptance system
Date: Mon, 3 Nov 2003 16:18:48 +0100 [thread overview]
Message-ID: <cdd31e6371940a5d0505fddfdf9a919e@plan9.escet.urjc.es> (raw)
In-Reply-To: <E1AGgD0-000GoQ-3I@t40.swtch.com>
[-- Attachment #1: Type: text/plain, Size: 71 bytes --]
Perhaps a tiny but different fs in the same machine could do the job.
[-- Attachment #2: Type: message/rfc822, Size: 2421 bytes --]
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] proposal: a patch acceptance system
Date: Mon, 03 Nov 2003 10:01:24 -0500
Message-ID: <E1AGgD0-000GoQ-3I@t40.swtch.com>
> term% patch/create ki-error /sys/src/cmd/ki/stats.c
> mkdir: can't create /n/sources/patch/ki-error: read-only filesystem
> mkdir /n/sources/patch/ki-error/ki-error failed
> term%
>
> Do I need to be in a special group on sources to be able to submit
> patches?
yes. oops. i'll have to rethink this.
i can't make a world-writable directory
on sources because then things like the
logs would also be world-writable, which
i definitely do not want.
the ki compile error is fixed anyway.
(pull again.)
next prev parent reply other threads:[~2003-11-03 15:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-02 17:01 andrey mirtchovski
2003-11-02 20:23 ` Russ Cox
2003-11-02 20:47 ` andrey mirtchovski
2003-11-03 10:16 ` Michael Giegerich
2003-11-03 15:05 ` Russ Cox
2003-11-17 10:25 ` Michael Giegerich
2003-11-03 13:56 ` kazumi iwane
2003-11-03 15:01 ` Russ Cox
2003-11-03 15:18 ` Fco.J.Ballesteros [this message]
2003-11-02 17:32 David Presotto
2003-11-02 17:45 ` a
[not found] <e89c2b9ccc6e9a8bfbc532c129cbc4c0@plan9.bell-labs.com>
2003-11-02 17:44 ` andrey mirtchovski
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=cdd31e6371940a5d0505fddfdf9a919e@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--cc=9fans@cse.psu.edu \
/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.
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).