From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17436 invoked by alias); 28 Oct 2003 00:22:45 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 17408 invoked from network); 28 Oct 2003 00:22:44 -0000 Received: from unknown (HELO nick.uklinux.net) (194.247.51.11) by sources.redhat.com with SMTP; 28 Oct 2003 00:22:44 -0000 Received: by nick.uklinux.net (Postfix, from userid 501) id 8210975FDE; Tue, 28 Oct 2003 01:15:09 +0000 (GMT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16285.49948.919736.737506@nick.uklinux.net> Date: Tue, 28 Oct 2003 00:22:00 -0000 To: gdb-patches@sources.redhat.com Subject: Re: PATCH (gdb/mi) X-SW-Source: 2003-10/txt/msg00800.txt.bz2 > > Eli will probably tell you that you need to update the MI doc's. > Thanks, that's a good catch. Yes, I should have told Nick that when > I saw the patch. I'll gladly do this but I thought that the patch needs to be approved first. Secondly, I have signed no copyright assignment for GDB (maybe this change is small enough not to need it). Finally the CONTRIBUTE file doesn't ask for documentation to be included when submitting a patch. Perhaps I've used the wrong subject header and it looks like the patch has already been committed. My impression now is that: RFC is for maintainers who ask for comments before committing their own patch. RFA is for those with write after approval. commit is for a patch that has been committed. and, rather oddly PATCH seems, generally, to be for a commit also. Most people who post to this list have some kind of write access to the repository. What subject header should someone without write authority use when submitting a patch? Some projects have a patch database as well as one for bugs. Would this be a good idea for GDB? Nick