From: "Petr Hluzín" <petr.hluzin@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Anitha Boyapati <anitha.boyapati@gmail.com>, gdb@sourceware.org
Subject: Re: Testing Call frame information in .debug_frame section
Date: Mon, 14 Feb 2011 22:43:00 -0000 [thread overview]
Message-ID: <AANLkTi=iSXXjaqc0gDSFgEMPN3Fbc9aZ40Ff5KiUz0Rj@mail.gmail.com> (raw)
In-Reply-To: <m3fwrqh8k8.fsf@fleche.redhat.com>
On 14 February 2011 17:42, Tom Tromey <tromey@redhat.com> 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. Then 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?)
--
Petr Hluzin
next prev parent reply other threads:[~2011-02-14 22:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 13:04 Anitha Boyapati
2011-02-13 2:34 ` Petr Hluzín
2011-02-13 9:57 ` Anitha Boyapati
2011-02-13 15:11 ` Petr Hluzín
2011-02-15 17:41 ` Richard Henderson
2011-02-15 18:09 ` Anitha Boyapati
2011-02-15 18:48 ` Richard Henderson
2011-02-15 19:15 ` Anitha Boyapati
2011-02-15 19:03 ` [avr] gas support for cfi info Richard Henderson
2011-02-15 22:45 ` Petr Hluzín
2011-02-16 17:59 ` Richard Henderson
2011-02-16 22:49 ` Petr Hluzín
2011-02-17 16:12 ` Richard Henderson
2011-02-17 16:16 ` Tristan Gingold
2011-02-17 15:35 ` Anitha Boyapati
2011-02-17 16:05 ` Richard Henderson
2011-02-17 19:53 ` Richard Henderson
2011-02-22 16:18 ` Anitha Boyapati
2011-02-22 17:51 ` Richard Henderson
2011-02-15 18:18 ` Testing Call frame information in .debug_frame section Anitha Boyapati
2011-02-15 22:12 ` Petr Hluzín
2011-02-14 16:42 ` Tom Tromey
2011-02-14 22:43 ` Petr Hluzín [this message]
2011-02-15 15:06 ` Tom Tromey
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='AANLkTi=iSXXjaqc0gDSFgEMPN3Fbc9aZ40Ff5KiUz0Rj@mail.gmail.com' \
--to=petr.hluzin@gmail.com \
--cc=anitha.boyapati@gmail.com \
--cc=gdb@sourceware.org \
--cc=tromey@redhat.com \
/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