From: Andrew STUBBS <andrew.stubbs@st.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Jim Blandy <jimb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: PATCH: Fix TUI null pointer dereference
Date: Mon, 31 Oct 2005 16:01:00 -0000 [thread overview]
Message-ID: <436605E0.2060309@st.com> (raw)
In-Reply-To: <20051030233223.GB1155@nevyn.them.org>
Daniel Jacobowitz wrote:
> You've got lots of pending patches (that I was going to review this
> weekend but ran out of time... it will get done this week). So, let's
> get you write access. Go to sourceware.org, look for the link that
> says "handy dandy little form", and list me as approver.
Thanks, I have submitted the form.
I also have quite a few patched queued at this end for your future
entertainment. I won't post them until I have finished tweaking and
testing and got the current lot out of the way.
Andrew Stubbs
next prev parent reply other threads:[~2005-10-31 11:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 14:28 Andrew STUBBS
2005-10-22 1:16 ` Jim Blandy
2005-10-24 13:32 ` Andrew STUBBS
[not found] ` <vt2pspuzwk3.fsf@theseus.home.>
2005-10-24 20:22 ` Andrew STUBBS
2005-10-31 11:56 ` Daniel Jacobowitz
2005-10-31 16:01 ` Andrew STUBBS [this message]
2005-10-31 20:34 ` Andrew STUBBS
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=436605E0.2060309@st.com \
--to=andrew.stubbs@st.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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