From: Joel Brobecker <brobecker@gnat.com>
To: David Lecomber <david@streamline-computing.com>
Cc: dan@debian.org, patches <gdb-patches@sources.redhat.com>
Subject: Re: [commit] Use full paths for "info sources"
Date: Sat, 16 Oct 2004 23:56:00 -0000 [thread overview]
Message-ID: <20041016235603.GC20779@gnat.com> (raw)
In-Reply-To: <1097712892.11117.75.camel@localhost.localdomain>
> > I haven't reviewed the entire thread yet. Was this something really
> > bad. Or is it just duplication we get in the output, and that's it?
>
> One problem is that things appear in the info sources, and info source,
> and in the stack traces, with different paths. So once you've got your
> definitive path for a file, you then see it referred to in a different
> way when you start using it. Work-roundable for the user I guess, but
> less than ideal.
I just had a look. I think I have a fix for it, but I might just have
opened a can of worms... In any case, I'm working on it.
--
Joel
next prev parent reply other threads:[~2004-10-16 23:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 14:22 David Lecomber
2004-09-21 15:30 ` Daniel Jacobowitz
2004-09-24 21:16 ` Joel Brobecker
2004-10-13 23:12 ` David Lecomber
2004-10-13 23:24 ` Joel Brobecker
2004-10-14 0:08 ` David Lecomber
2004-10-16 23:56 ` Joel Brobecker [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-19 22:57 Daniel Jacobowitz
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=20041016235603.GC20779@gnat.com \
--to=brobecker@gnat.com \
--cc=dan@debian.org \
--cc=david@streamline-computing.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