From: Michael Elizabeth Chastain <mec@shout.net>
To: fnasser@redhat.com, orjan.friberg@axis.com
Cc: gdb-patches@sources.redhat.com, gdb-testers@sources.redhat.com
Subject: Re: [RFA] Escape curly braces (Re: Sunday Project gdb test results, 2001-10-28)
Date: Mon, 29 Oct 2001 10:41:00 -0000 [thread overview]
Message-ID: <200110291841.MAA32065@duracef.shout.net> (raw)
I see the patch on the mainline, but not on gdb_5_1_2001-07-29-branch.
What is the policy for the 5.1 branch these days?
In the fullness of time I could setup my tests to do both mainline
and branch. But right now, I can handle just one configuration, and I
chose 5.1 branch. I can switch to mainline if that's more useful.
Michael Elizabeth Chastain
<mec@shout.net>
"love without fear"
next reply other threads:[~2001-10-29 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 10:41 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-29 3:37 Michael Elizabeth Chastain
2001-10-29 4:09 ` Orjan Friberg
[not found] <200110282001.OAA19612@duracef.shout.net>
2001-10-29 2:45 ` Orjan Friberg
2001-10-29 6:13 ` Fernando Nasser
2001-10-29 8:32 ` Orjan Friberg
2001-12-07 5:59 ` Orjan Friberg
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=200110291841.MAA32065@duracef.shout.net \
--to=mec@shout.net \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb-testers@sources.redhat.com \
--cc=orjan.friberg@axis.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