9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fmt and unicode text
Date: Sun, 16 Nov 2003 18:39:46 -0500	[thread overview]
Message-ID: <E1ALWUf-000ENx-4Z@t40.swtch.com> (raw)
In-Reply-To: Your message of "Sun, 16 Nov 2003 16:22:04 MST." <2147483647.1068999724@[192.168.42.6]>

> > I'd rather have a way that can (continue to) treat everyone equally.
> > Anyone who wants to submit a patch should be able to do it themselves,
> > without having to find someone to introduce it for them.  What you
> > suggest sounds reasonable at first glance but might be enough extra
> > work that it would discourage newcomers from bothering.  And newcomers
> > bearing patches are always a pleasant surprise, one that I'd prefer
> > not to discourage.
>
> How about an email address (9fans-patches@xxx ?) that just drops
> incoming messages into an IMAP mailbox that anyone can access
> anonymously? That way everyone can see the patches, test them out, etc.

that exists.  9fans@cse.psu.edu.  (for anonymous access, see google
or gmane.)

the reason i like the patch(1) system is that using the file server
makes it easy to put enough context there that patches can be applied
easily.  sure i could set it up to bundle up the various bits and
mail them somewhere, and write other tools to walk the mime attachments
and pull out the parts, but that's just using a mail system to do a
file system's job.

eventually i'll fix the problem correctly.
until then, i'd rather live without a solution than spend time building
a solution that solves the problem poorly.



  reply	other threads:[~2003-11-16 23:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-16 19:29 mirtchov
2003-11-16 21:23 ` Russ Cox
2003-11-16 21:51   ` mirtchov
2003-11-16 22:22     ` Russ Cox
2003-11-16 23:22       ` Lyndon Nerenberg
2003-11-16 23:39         ` Russ Cox [this message]
2003-11-16 21:28 ` David Presotto
2003-11-16 21:34   ` David Presotto
2003-11-16 21:52     ` mirtchov
2003-11-16 21:51   ` mirtchov

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=E1ALWUf-000ENx-4Z@t40.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).