From: Orjan Friberg <orjan.friberg@axis.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: New port: CRISv32
Date: Tue, 25 Jan 2005 15:03:00 -0000 [thread overview]
Message-ID: <41F65F89.7080404@axis.com> (raw)
In-Reply-To: <20050125144744.GA14468@nevyn.them.org>
Daniel Jacobowitz wrote:
>
> Those two ChangeLog entries were exactly the same... try again?
The gdbarch.h line was preceded by 8 spaces instead of a tab in the first one
(my mail client displays them differently). Or did you mean that both looked wrong?
--
Orjan Friberg
Axis Communications
next prev parent reply other threads:[~2005-01-25 15:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 9:51 Orjan Friberg
2005-01-14 17:42 ` Andrew Cagney
2005-01-25 14:40 ` Orjan Friberg
2005-01-25 14:45 ` Orjan Friberg
2005-01-25 14:48 ` Daniel Jacobowitz
2005-01-25 15:03 ` Orjan Friberg [this message]
2005-01-25 15:06 ` Daniel Jacobowitz
2005-01-25 16:23 ` Orjan Friberg
2005-01-25 17:03 ` Daniel Jacobowitz
2005-01-25 16:08 ` Andrew Cagney
2005-01-25 16:28 ` Orjan Friberg
2005-01-25 16:39 ` Andrew Cagney
2005-01-26 12:36 ` 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=41F65F89.7080404@axis.com \
--to=orjan.friberg@axis.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