From: Jonathan Larmour <jifl@eCosCentric.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: frame.c backtrace limit issue and fix
Date: Sun, 29 May 2005 01:59:00 -0000 [thread overview]
Message-ID: <429905B1.2040008@eCosCentric.com> (raw)
In-Reply-To: <20050528225136.GC22435@nevyn.them.org>
Daniel Jacobowitz wrote:
> You seem to be submitting patches against an old version; there already
> is a function named add_setshow_integer_cmd. Andrew added it in
> February.
Oops, yes it was against the most recent official release (6.3) not CVS. I
had to do the patch against 6.3 for my work, and didn't remember to switch
to CVS for the submission, my mistake.
[ker-snip]
> With all those fixed, I get the attached patch, which I've tested,
> regression tested, and checked in. Thanks.
Looks like you spent more effort on it than I did, so thank *you*!
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
prev parent reply other threads:[~2005-05-28 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 19:38 Jonathan Larmour
2005-05-28 23:09 ` Daniel Jacobowitz
2005-05-29 1:59 ` Jonathan Larmour [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=429905B1.2040008@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.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