From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb-patches@sources.redhat.com
Subject: Re: Fix varobj_update memleak
Date: Tue, 27 Feb 2007 23:43:00 -0000 [thread overview]
Message-ID: <17892.49688.699173.226288@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20070227230847.GA32390@caradoc.them.org>
> > Can I commit this change (in Vladimir's name)? I'm tired of backing it out
> > every time I do a commit on varobj.c.
>
> Yes, definitely. Thanks.
I've committed this change and my two patches. Thanks for keeping track of
them.
--
Nick http://www.inet.net.nz/~nickrob
prev parent reply other threads:[~2007-02-27 23:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 20:44 Vladimir Prus
2007-01-09 21:51 ` Daniel Jacobowitz
2007-02-27 22:34 ` Nick Roberts
2007-02-27 23:09 ` Daniel Jacobowitz
2007-02-27 23:43 ` Nick Roberts [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=17892.49688.699173.226288@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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