From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20197 invoked by alias); 8 Jan 2002 09:46:25 -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 20156 invoked from network); 8 Jan 2002 09:46:21 -0000 Received: from unknown (HELO dc-mx08.cluster1.charter.net) (209.225.8.18) by sources.redhat.com with SMTP; 8 Jan 2002 09:46:21 -0000 Received: from [24.241.47.50] (HELO localhost) by dc-mx08.cluster1.charter.net (CommuniGate Pro SMTP 3.4.6) with ESMTP id 68442281; Tue, 08 Jan 2002 04:54:16 -0500 Received: from kdienes by localhost with local (Exim 3.33 #1 (Debian)) id 16Nspm-00012b-00; Tue, 08 Jan 2002 04:46:18 -0500 From: Klee Dienes Reply-To: Klee Dienes To: Michael Snyder Cc: gdb-patches@sources.redhat.com Subject: Re: [PATCH] tracepoint.c References: <200201080149.g081nHw00463@reddwarf.cygnus.com> Date: Tue, 08 Jan 2002 01:46:00 -0000 In-Reply-To: <200201080149.g081nHw00463@reddwarf.cygnus.com> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-01/txt/msg00132.txt.bz2 Michael Snyder writes: > 2002-01-07 Michael Snyder > > * tracepoint.c (tracepoint_save_command): From Klee Dienes -- > use tilde_expand and strerror for opening save-tracepoints file. > Just to make sure I understand the procedure I should be following: Does this mean that I should re-submit a version of the 'save-breakpoints' patch with this change removed from it? Or does it just mean that this part of the patch has been accepted, and I should wait to hear from the other relevant maintainers before revising or committing the rest of the save-breakpoint patch? If the latter, why not just say "the changes to tracepoint.c are approved; please commit them"? I don't mean this as complaint, just trying to make sure I'm following the system properly. Also, is there a formalized way to ping or somehow track already submitted patches? We've got a number of other patches pretty much ready to submit (the Objective-C patches being the most notable of these), but since they depend on some of the patches already submitted, I was hoping to get these resolved first. Should I just go ahead and post them, with a note that they assume that some of the already-submitted patches have been committed? This can get to be a real mess eventually, as when I modify one patch in response to feedback, I then have to go modify all the dependent patches. Or should I just badger individual maintainers until the ones already submitted have been resolved? I realize the irony of showing up after years of code-divergence, and then being in a big "rush rush rush" mode to get patches considered for acceptance. But I'm sure we (the Apple GDB engineers) only have a limited window of oppotunity before some other crisis comes up to distract us, and I'm hoping to take as much advantage of this opportunity to merge the sources as I possibly can. Thanks, - Klee