public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Chad Walstrom <chewie@wookimus.net>
To: help-gnats@gnu.org
Subject: Re: gnatsd problems with 4.0.1
Date: Thu, 06 Jan 2005 17:07:00 -0000	[thread overview]
Message-ID: <20050106170435.GA2921@wookimus.net> (raw)
In-Reply-To: <20050106111441.64c255e3.mishka@apk.od.ua>


[-- Attachment #1.1: Type: text/plain, Size: 1098 bytes --]

Mike M. Volokhov wrote:
> Could you explain me please what a reason to have libiberty code in
> GNATS tree?

For historical and supposedly portability reasons.  Frankly, I'm not
that comfortable with it being there.  I haven't had much time lately,
but I'd love to audit the GNATS codebase to find out what functions in
./libiberty are actually being used and decide either to adopt them
completely by moving them into the ./gnats directory OR drop them
completely.  There was a lot of cruft pulled in from my last update.  We
can always roll back the CVS to the point before the libiberty update
(which I've been contemplating since the day I mistakenly committed it
to TRUNK rather than the dev branch like I wanted).

Any opinions in either direction?

If someone is willing to do the audit, let me know.  It may not take
much time, but most of my spare time right now is going toward a
certification class, :-/, and caring for my son, :-).

-- 
Chad Walstrom <chewie@wookimus.net>           http://www.wookimus.net/
           assert(expired(knowledge)); /* core dump */

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats

  reply	other threads:[~2005-01-06 17:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05 18:23 Tim Buck
2005-01-05 22:24 ` Chad Walstrom
2005-01-06  9:18   ` Mike M. Volokhov
2005-01-06 17:07     ` Chad Walstrom [this message]
2005-02-07 15:47       ` Mike M. Volokhov
2005-02-07 17:15         ` Mark D. Baushke
2005-02-07 19:17           ` Chad Walstrom
2005-02-09 12:50           ` Removing libiberty (was Re: gnatsd problems with 4.0.1) Mike M. Volokhov
2005-02-09 17:15             ` Mark D. Baushke
2005-02-07 17:45         ` Chad Walstrom
2005-02-09 10:56           ` Mike M. Volokhov
     [not found]             ` <20050221235730.GC31157@wookimus.net>
     [not found]               ` <20050222175714.30bc1593.mishka@apk.od.ua>
2005-02-24 22:17                 ` Soon to come: RC3 Chad Walstrom
2005-02-24 22:40                   ` RC2 (was Re: Soon to come: RC3) Chad Walstrom
2005-01-06 16:03   ` gnatsd problems with 4.0.1 Tim Buck

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=20050106170435.GA2921@wookimus.net \
    --to=chewie@wookimus.net \
    --cc=help-gnats@gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).