From: Elena Zannoni <ezannoni@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb@sources.redhat.com
Subject: Re: New directory src/gdb/misc?
Date: Thu, 07 Mar 2002 06:55:00 -0000 [thread overview]
Message-ID: <15495.32556.289737.444380@localhost.redhat.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020307081119.8027K-100000@is>
Eli Zaretskii writes:
>
> On Thu, 7 Mar 2002, Daniel Jacobowitz wrote:
>
> > > This leaves ``gdb/common'' and, (new suggestion) gdb/misc/ as possible
> > > directory names.
> >
> > 'misc' doesn't convey any information. It's like calling something
> > 'new' in its documentation - not useful for very long. I'd vote for
> > common.
>
> Either `common' or maybe `lib' (or `gdblib'). I agree that `misc' is not
> such a good idea.
how about 'generic' (stolen from gdbtk) or 'shared' or 'general' ?
Elena
next prev parent reply other threads:[~2002-03-07 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 18:31 Andrew Cagney
2002-03-06 21:31 ` Daniel Jacobowitz
2002-03-06 22:13 ` Eli Zaretskii
2002-03-06 22:31 ` Andrew Cagney
2002-03-07 6:55 ` Elena Zannoni [this message]
2002-03-07 7:59 ` Andrew Cagney
2002-03-07 10:44 ` Daniel Jacobowitz
2002-03-06 22:22 ` Andrew Cagney
2002-03-07 10:42 ` 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=15495.32556.289737.444380@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=drow@mvista.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@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