From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] fmt and unicode text In-Reply-To: Your message of "Sun, 16 Nov 2003 16:22:04 MST." <2147483647.1068999724@[192.168.42.6]> From: "Russ Cox" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <55299.1069025986.1@t40.swtch.com> Message-Id: Date: Sun, 16 Nov 2003 18:39:46 -0500 Topicbox-Message-UUID: 8cdeabfa-eacc-11e9-9e20-41e7f4b1d025 > > 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.