Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Jim Blandy <jimb@red-bean.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix gdb.asm/asm-source.exp for hppa64-hpux
Date: Thu, 01 Dec 2005 05:47:00 -0000	[thread overview]
Message-ID: <438E8E5F.6070209@tausq.org> (raw)
In-Reply-To: <8f2776cb0511302141q6629a801laf783dcddb7a973d@mail.gmail.com>

> Is there a plausible place to put a comment explaining this constraint?

I can add comments to common.inc, pa.inc/pa64.inc or asm-source.exp. Any
preferences?

> Strictly speaking, you should submit the indentation change and the
> pa64.inc as separate changes.

ok, i'll wait for comments for the above and send this again.

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/


  reply	other threads:[~2005-12-01  5:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <438E3C26.4010805@tausq.org>
2005-12-01  5:41 ` Jim Blandy
2005-12-01  5:47   ` Randolph Chung [this message]
2005-12-01  5:55     ` Jim Blandy
2005-12-01 14:27       ` Daniel Jacobowitz
2005-12-01 15:33         ` Randolph Chung
2005-12-02  1:07           ` Jim Blandy

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=438E8E5F.6070209@tausq.org \
    --to=randolph@tausq.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@red-bean.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