From: Daniel Jacobowitz <drow@false.org>
To: "Veeru (????????????)" <misterveeru@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: GDB source structure
Date: Fri, 01 Sep 2006 20:26:00 -0000 [thread overview]
Message-ID: <20060901202639.GA22174@nevyn.them.org> (raw)
In-Reply-To: <ee4c53600609011324u4170f512pe88c25064fca8579@mail.gmail.com>
On Fri, Sep 01, 2006 at 01:24:19PM -0700, Veeru (????????????) wrote:
> Hi Dan,
>
> The set of files is reaching close to 600 in number in that directory.
> At this point,
> even doing an ls is difficult, forget separating out different
> architectures and operating systems.
> Some file names have the architecture or OS name in them but even that
> usage is not consistent.
Yes, it is. It's extremely consistent. The files which are specific
to an architecture or OS are named after that architecture or OS.
I don't know of any exceptions.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-09-01 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ee4c53600609011321k5a7a538fp933250cc13bb58d6@mail.gmail.com>
2006-09-01 20:24 ` Veeru (वीऱू)
2006-09-01 20:26 ` Daniel Jacobowitz [this message]
2006-09-01 20:57 ` Michael Snyder
2006-09-02 15:28 ` Eli Zaretskii
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=20060901202639.GA22174@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=misterveeru@gmail.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