9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: uriel@cat-v.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] newaccount.html has gone missing
Date: Tue,  7 Mar 2006 14:23:23 +0100	[thread overview]
Message-ID: <3be98932eb2de4113901b957b015932e@cat-v.org> (raw)

>> The problem is that that somewhat breaks patch(1), it still
>> works but spills a bunch of errors because it can't chmod
>> any files, and it shows up as created by none.
>
> then please submit a patch for patch.  patches need to be
> possible to create as none.
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.

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.

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?

>> > you need to run 9fs sources; mount /srv/sources /n/sources
>> Question is, should we change patch(1) to do that?
>
> definitely not.  patches need to be possible to create as none.
> i think people with sources accounts should just change their
> /rc/bin/9fs scripts.  it's a good exercise.
Yes, except that then you have a file permanently out of sync with
sources, and the ensuing troubles with replica.

> the auto-account-creator was a clumsy hack that was
> difficult to maintain.  we were only using accounts as
> proof-of-clickthrough.  now that the clickthrough is gone,
> the need for accounts is gone too.
Yes, I think everyone is happy to see it gone.

> we'll still create accounts as necessary for people who
> need to write to sources (e.g., in contrib or other places).
> frequent patch submitters are welcome to ask too.
This seems reasonable to me.

uriel



             reply	other threads:[~2006-03-07 13:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-07 13:23 uriel [this message]
2006-03-07 13:45 ` Russ Cox
  -- 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=3be98932eb2de4113901b957b015932e@cat-v.org \
    --to=uriel@cat-v.org \
    --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).