9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: a@9srv.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] proposal: a patch acceptance system
Date: Sun,  2 Nov 2003 12:45:25 -0500	[thread overview]
Message-ID: <cb7aa9aa548849d571206c1231e8bb4d@9srv.net> (raw)
In-Reply-To: <592643f7ffafc790c9482d76f00a4b23@plan9.bell-labs.com>

i understand (and second, as far as it goes) presotto's concern
regarding matching patch versions. what the scheme andry described
would rely on in order to avoid that is some level of responsability
on the part of the patch submitter to make sure they're patching
current code, some care on the part of sources-pushers to see if
there's outstanding patches their changes are affecting (in which
case they should at least notify the submitter), and some promptness
on the part of whoever's responsable for the code being affected.
certainly this is a bit of attention by all parties, but i think it's
the best way (of suggestions i've heard) to make sure changes can get
put in or rejected quickly, and the reasons for rejections understood,
without putting a very large burdon on any one of the three above
parties.
ア


  reply	other threads:[~2003-11-02 17:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-02 17:32 David Presotto
2003-11-02 17:45 ` a [this message]
     [not found] <e89c2b9ccc6e9a8bfbc532c129cbc4c0@plan9.bell-labs.com>
2003-11-02 17:44 ` andrey mirtchovski
  -- strict thread matches above, loose matches on Subject: below --
2003-11-02 17:01 andrey mirtchovski
2003-11-02 20:23 ` Russ Cox
2003-11-02 20:47   ` andrey mirtchovski
2003-11-03 10:16     ` Michael Giegerich
2003-11-03 15:05       ` Russ Cox
2003-11-17 10:25         ` Michael Giegerich
2003-11-03 13:56   ` kazumi iwane
2003-11-03 15:01     ` Russ Cox
2003-11-03 15:18       ` Fco.J.Ballesteros

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=cb7aa9aa548849d571206c1231e8bb4d@9srv.net \
    --to=a@9srv.net \
    --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).