> 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
