Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org, gregory.0xf0@gmail.com
Subject: Re: gnulib's errno module was imported
Date: Fri, 14 Nov 2014 07:33:00 -0000	[thread overview]
Message-ID: <83389mjkxk.fsf@gnu.org> (raw)
In-Reply-To: <87oasaibe6.fsf@codesourcery.com>

> From: Yao Qi <yao@codesourcery.com>
> CC: <gregory.0xf0@gmail.com>
> Date: Fri, 14 Nov 2014 13:44:49 +0800
> 
> I am inclined to back "dirfd" (and "errno") module out.  As a result,
> gdb will not be compatible with LSB 3.0, but it is just a minor issue to
> me.  What do you think?

Is it possible to back out dirfd, and then add to GDB whatever glue
(borrowed from gnulib) that's needed to support LSB 3.0?  IOW, can we
support LSB 3.0 in our own code, either inspired or stolen from
gnulib?

IME, gnulib many times includes a lot of overhead in its solutions for
problems, while the minimal change to fix the specific problem can be
much more lightweight and simple.  the question is can we go this way
in this case?

Thanks.


  reply	other threads:[~2014-11-14  7:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14  5:45 Yao Qi
2014-11-14  7:33 ` Eli Zaretskii [this message]
2014-11-14  8:30   ` Yao Qi
2014-11-14  8:44     ` Gregory Fong
2014-11-14  9:26     ` Eli Zaretskii
2014-11-14 11:29 ` Joel Brobecker
2014-11-14 11:47 ` Pedro Alves
2014-11-14 13:02   ` Yao Qi
2014-11-14 13:21     ` Pedro Alves
2014-11-14 13:54       ` Yao Qi
2014-11-14 14:39         ` Pedro Alves
2014-11-14 15:18           ` Joel Brobecker
2014-11-14 16:01             ` Pedro Alves
2014-11-14 23:08               ` Yao Qi
2014-11-14 14:31       ` Eli Zaretskii
2014-11-14 14:42         ` Pedro Alves

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=83389mjkxk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=gregory.0xf0@gmail.com \
    --cc=yao@codesourcery.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