From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28491 invoked by alias); 14 Feb 2011 22:43:58 -0000 Received: (qmail 28483 invoked by uid 22791); 14 Feb 2011 22:43:57 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-fx0-f41.google.com (HELO mail-fx0-f41.google.com) (209.85.161.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 14 Feb 2011 22:43:52 +0000 Received: by fxm12 with SMTP id 12so6008627fxm.0 for ; Mon, 14 Feb 2011 14:43:49 -0800 (PST) Received: by 10.223.83.199 with SMTP id g7mr4038542fal.97.1297723429697; Mon, 14 Feb 2011 14:43:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.55.154 with HTTP; Mon, 14 Feb 2011 14:43:29 -0800 (PST) In-Reply-To: References: From: =?UTF-8?B?UGV0ciBIbHV6w61u?= Date: Mon, 14 Feb 2011 22:43:00 -0000 Message-ID: Subject: Re: Testing Call frame information in .debug_frame section To: Tom Tromey Cc: Anitha Boyapati , gdb@sourceware.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-02/txt/msg00068.txt.bz2 On 14 February 2011 17:42, Tom Tromey wrote: >... > Petr> Just go to binutils web and search for my name in the patch tracker. > Petr> Oh wait, they do not have one. Maybe this is the reason they forgot= to > Petr> reply to my patches. > > You have to ping patches, not just for binutils but also gdb and gcc. > It isn't a great system but it does have its advantages. One advantage is that people can write replies inline into the patch. However this practice is fairly common so I bet patch-trackers can be configured to include the submitted patch when mailing a notification to a mailing list. Savannah's tools look quite capable. Are there more advantages? Are they pretty common? Is there an automatized solution for them, yet? > One or two weeks after an initial submission, if there has been no > answer, just send a ping message as a follow-up to your patch. =C2=A0Then= do > it every week. This sounds quite mechanical, boring and common to a lot of people (submitters). Great example of task suitable for machines. (Why do you people choose such suffering?) --=20 Petr Hluzin