Re: Patch submission process

[Phil Edwards <phil at jaj dot com>]

On Sat, Mar 15, 2003 at 12:40:39AM -1000, Glen Nakamura wrote:
> On Sat, Mar 15, 2003 at 10:44:42AM +0100, Andreas Jaeger wrote:
> > NOrmally the person approving the patch should commit it.  Otherwise
> > just ask around.
> > 
> I really haven't had much difficulty getting a patch committed once it
> was approved.  I was just wondering if there was a standard procedure.
> It does occur to me that the people reviewing patches are busy enough
> already, and it may be helpful to have a patch queue where other people
> with write privileges could bootstrap, regression test, and commit patches
> when they find time.

Bootstrapping and testing is the responsibility of the person submitting
the patch.  A queue for "has been approved, needs to be committed" is a
lot more feasible if all a committer needs to do is retrieve, apply, checkin.

In the usual case, though, Andreas's comment applies:  the approver does
the checkin for those who do not have write privs.


> Perhaps it will possible after switching to bugzilla?

It's /possible/ now; we just need to do it.  I don't think bugzilla will
make this any easier or different.

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