public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>,
	gcc@gcc.gnu.org, Fergus Henderson <fjh@cs.mu.OZ.AU>,
	Mark Mitchell <mark@codesourcery.com>,
	Gabriel Dos Reis <gdr@integrable-solutions.net>
Subject: Re: review process
Date: Mon, 31 Mar 2003 18:13:00 -0000	[thread overview]
Message-ID: <20030331170450.GA15096@disaster.jaj.com> (raw)
In-Reply-To: <C8237DA1-6392-11D7-8FBD-000393575BCC@dberlin.org>


Moving to gcc@.


On Mon, Mar 31, 2003 at 11:06:50AM -0500, Daniel Berlin wrote:
> 
> If we could
> 1. Be okay with the idea that any patch not submitted in a reasonable 
> format (IE changelog + patch in message, or changelog in message + 
> attached file with patch), and with [PATCH] in the subject line, 
> wouldn't be tracked.

This seems obvious.

> 2. Be okay with the idea that: patches approved by people without 
> reasonable mailers (reasonable being those that can tell us whether a 
> message is a reply to another message), when it's not easily detectable 
> otherwise, will be assumed to not be approved.

There are only two or three people in the MAINTAINERS file that have
mailers like this.  This sounds good too (democracy at work).


> 3. Standardize the text + possible placement of approval messages.
> 
> then I'm pretty sure i could auto-track missed patches.
> 
> But it's worthless if we can't detect already-approved patches, thus 
> the need to come up with a format for approval messages.
> 
> Obviously, i don't need something in some strict format, I just need to 
> be able to determine that a given message containing patch was approved 
> (or approved with changes, etc).  Thus, simply saying that approval 
> messages should contain a line starting with "approved".

Most such systems also have a "stop processing" keyword or phrase, e.g.,

    approved
    thankyou

    J.Random User wrote:
    > Here's my patch, yadda yadda yadda.

    Please also consider a followup patch that makes this work on platforms
    which do not necessarily obey the laws of physics during runtime loading.


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

  reply	other threads:[~2003-03-31 16:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3r88o255d.fsf@uniton.integrable-solutions.net>
     [not found] ` <1049055987.31893.378.camel@doubledemon.codesourcery.com>
     [not found]   ` <m3r88oy3we.fsf@uniton.integrable-solutions.net>
     [not found]     ` <1049059174.31893.385.camel@doubledemon.codesourcery.com>
     [not found]       ` <m3d6k8y2eg.fsf@uniton.integrable-solutions.net>
     [not found]         ` <1049059963.7575.391.camel@doubledemon.codesourcery.com>
     [not found]           ` <m34r5ky1wc.fsf@uniton.integrable-solutions.net>
     [not found]             ` <1049060738.31975.394.camel@doubledemon.codesourcery.com>
     [not found]               ` <20030331041419.GA4687@ceres.cs.mu.oz.au>
     [not found]                 ` <20030331060732.GA10362@disaster.jaj.com>
     [not found]                   ` <20030331062256.GA6493@ceres.cs.mu.oz.au>
2003-03-31 10:08                     ` Gerald Pfeifer
2003-03-31 17:50                       ` Daniel Berlin
2003-03-31 18:13                         ` Phil Edwards [this message]
2003-03-31 18:45                           ` Daniel Berlin
2003-03-31 18:42                         ` Tom Tromey
2003-03-31 20:06                         ` Alexandre Oliva
2003-03-31 20:08                           ` Daniel Berlin
2003-03-31 21:02                             ` Alexandre Oliva
2003-04-02 17:15                         ` Hans-Peter Nilsson
2003-03-31 19:52 Nathanael Nerode
2003-03-31 20:02 ` Richard Henderson

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=20030331170450.GA15096@disaster.jaj.com \
    --to=phil@jaj.com \
    --cc=dberlin@dberlin.org \
    --cc=fjh@cs.mu.OZ.AU \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    --cc=mark@codesourcery.com \
    --cc=pfeifer@dbai.tuwien.ac.at \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).