From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] newaccount.html has gone missing
Date: Tue, 7 Mar 2006 08:45:53 -0500 [thread overview]
Message-ID: <5d283727139e5e27637ba054431ffbdd@swtch.com> (raw)
In-Reply-To: <3be98932eb2de4113901b957b015932e@cat-v.org>
> Would anyone complain if the email address is a required argument to
> patch/create? If someone really doesn't want to provide a real email
> address they can always provide a random string.
Did this.
> While we are at it, would it be ok if I moved the new patches
> into an /incoming directory rather than keeping them in the top level
> patch/ dir?
Will not do this. It is just not hard to do
ls | grep -v '^(applied|saved|sorry)$'
or to test -f $d/files. I type these paths a lot
and don't want to type /incoming/ in the common case.
> They can be created as none, but various things won't work, eg.,
> you can't edit/delete it after you create it, and you can't chmod any
> of the files either.
It's true you can't chmod (wstat). You can still edit and delete it.
I just tried to make sure. I have silenced the chmods.
> Yes, except that then you have a file permanently out of sync with
> sources, and the ensuing troubles with replica.
You already have files permanently out of sync with sources.
These include /lib/ndb/local and /mail/lib/rewrite. We fully
expect people to edit these and /rc/bin/9fs locally and we
promise to change them only rarely. There are no "ensuing troubles"
as long as you tell replica to ignore changes to the particular file.
Doing so is even easier with the new command line options.
Russ
next prev parent reply other threads:[~2006-03-07 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 13:23 uriel
2006-03-07 13:45 ` Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-19 19:20 Russ Cox
2006-02-22 2:22 ` Frank Gleason
2006-02-19 6:06 Frank Gleason
2006-02-19 6:45 ` geoff
2006-02-19 8:50 ` uriel
2006-02-19 8:55 ` geoff
2006-02-19 9:17 ` jmk
2006-02-19 9:18 ` andrey mirtchovski
2006-02-19 10:25 ` uriel
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=5d283727139e5e27637ba054431ffbdd@swtch.com \
--to=rsc@swtch.com \
--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).