From: Tom Tromey <tromey@redhat.com>
To: Valery Khromov <valery.khromov@gmail.com>
Cc: gdb-patches@sourceware.org, Pedro Alves <alves.ped@gmail.com>,
Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: [PATCH v2] Fix PR gdb/12953: No hardware watchpoints on FreeBSD amd64
Date: Wed, 01 Feb 2012 20:27:00 -0000 [thread overview]
Message-ID: <m3d39y8fl3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <045981A0-EA00-4DC4-B16A-A9FEB3C87494@gmail.com> (Valery Khromov's message of "Tue, 31 Jan 2012 19:49:27 +0300")
>>>>> "Valery" == Valery Khromov <valery.khromov@gmail.com> writes:
Valery> I have copyright assignment paperwork finished.
Valery> What should I do next?
I re-read the thread and I think there is still an unfulfilled request:
http://sourceware.org/ml/gdb-patches/2011-12/msg00695.html
Other than that, wait for review.
Feel free to ping a complete patch weekly until someone responds.
Tom
next prev parent reply other threads:[~2012-02-01 20:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 2:41 [PATCH] " Valery Khromov
2011-12-20 14:52 ` Tom Tromey
2011-12-20 18:30 ` Valery Khromov
2011-12-21 6:45 ` Joel Brobecker
2011-12-20 15:04 ` Mark Kettenis
2011-12-20 16:12 ` Pedro Alves
2011-12-20 17:52 ` Valery Khromov
2011-12-20 17:53 ` [PATCH 1/2] FreeBSD/amd64: Updates for the recent changes that Pedro Alves made Valery Khromov
2011-12-20 17:56 ` [PATCH 2/2] FreeBSD: Removed definition of DBREG_DRX macro because it is already in FreeBSD Valery Khromov
2011-12-20 19:44 ` [PATCH] Fix PR gdb/12953: No hardware watchpoints on FreeBSD amd64 Mark Kettenis
2011-12-20 20:38 ` [PATCH v2] " Valery Khromov
2012-01-31 17:50 ` Valery Khromov
2012-02-01 20:27 ` Tom Tromey [this message]
2012-02-02 9:03 ` Valery Khromov
2012-02-11 18:51 ` Mark Kettenis
2012-02-11 21:03 ` Valery Khromov
2012-02-09 16:10 ` Pedro Alves
2011-12-20 16:05 ` [PATCH] " Pedro Alves
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=m3d39y8fl3.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=alves.ped@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=valery.khromov@gmail.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