From: Nick Roberts <nickrob@snap.net.nz>
To: "Robert Norton" <rnorton@broadcom.com>
Cc: gdb@sourceware.org
Subject: Re: FW: (Another) Segfault in varobj.c
Date: Tue, 07 Aug 2007 21:47:00 -0000 [thread overview]
Message-ID: <18104.59508.761105.593329@kahikatea.snap.net.nz> (raw)
In-Reply-To: <B0D822BFECD50F4991F2516EA50F273C021ABDF3@NT-IRVA-0752.brcm.ad.broadcom.com>
> > I can't say how risky it would be, I don't even understand
> > why you would rather
> > backport to 6.6 than update to 6.7.
>
> I didn't think 6.7 had been released yet?
No but it was scheduled for release in July. I think current CVS is fairly
stable and recent changes have been conservative, so you probably could just
merge to that and get better results than with 6.6.
--
Nick http://www.inet.net.nz/~nickrob
prev parent reply other threads:[~2007-08-07 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 13:21 Robert Norton
2007-08-07 21:47 ` 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=18104.59508.761105.593329@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb@sourceware.org \
--cc=rnorton@broadcom.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