This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Testing Call frame information in .debug_frame section
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