From: msnyder@sonic.net
To: "Nick Roberts" <nickrob@snap.net.nz>
Cc: msnyder@sonic.net, gdb-patches@sourceware.org
Subject: Re: [resubmit] memory leak, mi-cmd-var
Date: Fri, 29 Jun 2007 11:34:00 -0000 [thread overview]
Message-ID: <5330.12.7.175.2.1183096279.squirrel@webmail.sonic.net> (raw)
In-Reply-To: <18052.38305.461372.362123@kahikatea.snap.net.nz>
> The conservative approach would be to wait until after the release, or at
> least the branch/branchpoint.
That's perfectly reasonable -- I certainly don't object to holding these
patches for after the branchpoint, and I won't check any more in as
"obvious".
Just let's not have them fall thru a crack... ;-)
Michael
prev parent reply other threads:[~2007-06-29 5:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 5:16 msnyder
2007-06-29 5:51 ` Nick Roberts
2007-06-29 11:34 ` msnyder [this message]
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=5330.12.7.175.2.1183096279.squirrel@webmail.sonic.net \
--to=msnyder@sonic.net \
--cc=gdb-patches@sourceware.org \
--cc=nickrob@snap.net.nz \
/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