Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@redhat.com
Cc: brobecker@gnat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA/commit] Add new file hppa-hpux-tdep.c
Date: Fri, 13 Dec 2002 13:29:00 -0000	[thread overview]
Message-ID: <3099-Fri13Dec2002231543+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <3DFA4655.6050007@redhat.com> (message from Andrew Cagney on Fri, 13 Dec 2002 15:43:01 -0500)

> Date: Fri, 13 Dec 2002 15:43:01 -0500
> From: Andrew Cagney <ac131313@redhat.com>
> 
> >   - There is also this fnchange.lst file, which I don't understand
> >     completely. The documentation says I should add a new line for
> >     each file that does not respect the 8.3 format. But it does not
> >     say what should be there. I thought it should be @V.../longname
> >     followed by @V.../8+3name. But I saw many exceptions, and many
> >     entries missing. So I'm not sure what I should do for this patch.
> >     Eli?
> 
> Only the files with 8.3 name clashes need a rename.

Right.  Also, file names that include characters which are disallowed
by DOS 8+3 filesystems, like `+'.

> So areallylongfilename.c is ok provided there isn't also
> areallylongsecondfilename.c :-)

Yes.

> (perhaps the doco needs clarifying?)

If a GDB developer cannot figure this out, I'd say a calrification is
in order.


  reply	other threads:[~2002-12-13 21:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-13 10:10 Joel Brobecker
2002-12-13 12:47 ` Andrew Cagney
2002-12-13 13:29   ` Eli Zaretskii [this message]
2002-12-16  9:03 ` Joel Brobecker

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=3099-Fri13Dec2002231543+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=ac131313@redhat.com \
    --cc=brobecker@gnat.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