Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
	jan.kratochvil@redhat.com,        gdb-patches@sourceware.org
Subject: Re: [patch 1/2] libunwind/ia64: Rename libunwind-frame.[ch]
Date: Tue, 06 Mar 2012 09:44:00 -0000	[thread overview]
Message-ID: <4F55DC4A.5020108@redhat.com> (raw)
In-Reply-To: <0EAB4374-907D-4ACD-85F6-089DB5E22BA8@adacore.com>

On 03/06/2012 09:00 AM, Tristan Gingold wrote:

> 
> On Mar 6, 2012, at 9:43 AM, Mark Kettenis wrote:
> 
>>> Date: Tue, 06 Mar 2012 07:54:35 +0000
>>> From: Pedro Alves <palves@redhat.com>
>>>
>>> In patch #1 rename libunwind-frame.h -> ia64-tdep-libunwind-frame.h
>>
>> BTW, is it just me, or do other people think as well that
>> ia64-tdep-libunwin-frame.h is an awfully long name?
> 
> Yes, it is but I am unable to find a better shorter oneÂ…


I could live quite well without the tdep bit, thus, ia64-libunwind-frame.[hc];
or, since we're really using libunwind's libunwind-ia64.h and libunwind-ia64.so,
we could also go with libunwind-ia64-frame.[hc].

-- 
Pedro Alves


  reply	other threads:[~2012-03-06  9:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04 21:58 Jan Kratochvil
2012-03-06  7:54 ` Pedro Alves
2012-03-06  8:43   ` Mark Kettenis
2012-03-06  8:45     ` Jan Kratochvil
2012-03-06  9:00     ` Tristan Gingold
2012-03-06  9:44       ` Pedro Alves [this message]
2012-03-06  9:53         ` Jan Kratochvil
2012-03-06 10:35           ` Pedro Alves
2012-03-06 10:48           ` Mark Kettenis
2012-03-06 11:32             ` Jan Kratochvil
2012-03-06 11:43               ` Pedro Alves
2012-03-08  9:15   ` Jan Kratochvil
2012-03-08 10:40     ` Pedro Alves

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=4F55DC4A.5020108@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gingold@adacore.com \
    --cc=jan.kratochvil@redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    /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