From: Doug Evans <dje@transmeta.com>
To: gdb-patches@sources.redhat.com
Cc: brolley@redhat.com, fche@redhat.com, cgen@sources.redhat.com
Subject: Re: [PATCH] remove .cpu file copying
Date: Fri, 05 Sep 2003 16:31:00 -0000 [thread overview]
Message-ID: <16216.44823.591234.896898@casey.transmeta.com> (raw)
In-Reply-To: <200309051534.IAA17701@casey.transmeta.com>
Doug Evans writes:
> [btw, is there a plan to delete sim/i960 from the 6.0 branch?]
pedantic: by "delete" I mean s,^,//OBSOLETE, of course.
next prev parent reply other threads:[~2003-09-05 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 15:44 Doug Evans
2003-09-05 16:31 ` Doug Evans [this message]
2003-09-05 17:22 ` Andrew Cagney
2003-09-05 19:03 ` Andrew Cagney
2003-09-06 7:05 ` Dave Brolley
[not found] ` <16216.57078.426082.733525@casey.transmeta.com>
[not found] ` <3F58FC5C.90207@redhat.com>
[not found] ` <16217.157.59117.344696@casey.transmeta.com>
2003-09-06 14:13 ` Nick Clifton
[not found] ` <16217.35254.503075.467627@casey.transmeta.com>
2003-09-09 3:42 ` Dave Brolley
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=16216.44823.591234.896898@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=brolley@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=fche@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).