From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: kris <cq.personal@gmail.com>,
38364@debbugs.gnu.org, 38368@debbugs.gnu.org
Subject: bug#38364: bug#38368: gcc/ dlclose() documentation feedback
Date: Tue, 31 Dec 2019 11:48:14 +0100 [thread overview]
Message-ID: <87h81gbwk1.fsf@marxist.se> (raw)
In-Reply-To: <87tv6rig02.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 26 Nov 2019 02:27:25 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> kris <cq.personal@gmail.com> writes:
>
>> I think there is some ambiguity in the man page for dlclose().
>
> This bug report landed in the Emacs bug tracker -- perhaps because of
> the debbugs.gnu.org outage yesterday?
>
> What package was this bug report meant for?
This seems to be intended for glibc, but they do not use debbugs
according to: https://sourceware.org/glibc/wiki/FilingBugs
I can't figure out how to forward a bug to them without creating an
account here: https://sourceware.org/bugzilla/enter_bug.cgi
The original submitter of the bug is in the best position to file a
bug using their web interface, but has unfortunately not reported back
here within 5 weeks. I'm therefore not sure how to best proceed here.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2019-12-31 10:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 1:58 bug#38368: gcc/ dlclose() documentation feedback kris
2019-11-26 1:27 ` Lars Ingebrigtsen
2019-12-31 10:48 ` Stefan Kangas [this message]
2019-12-31 10:49 ` bug#38364: " Lars Ingebrigtsen
2019-12-31 10:53 ` Stefan Kangas
2020-01-01 10:58 ` Stefan Kangas
2020-01-07 20:43 ` bug#38368: " Carlos O'Donell
[not found] ` <handler.38368.B.157468668921327.ack@debbugs.gnu.org>
2019-11-26 2:48 ` bug#38368: Acknowledgement (gcc/ dlclose() documentation feedback) kris
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h81gbwk1.fsf@marxist.se \
--to=stefan@marxist.se \
--cc=38364@debbugs.gnu.org \
--cc=38368@debbugs.gnu.org \
--cc=cq.personal@gmail.com \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).