public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Konstantin Kharlamov <Hi-Angel@yandex.ru>
To: "Lukáš Jiřiště" <gymnazium.jiriste@gmail.com>, libc-help@sourceware.org
Subject: Re: Where to send issues
Date: Wed, 24 Jan 2024 11:15:26 +0300	[thread overview]
Message-ID: <7f7e6e9ad516d189fd073c3d078eec5d9d77643e.camel@yandex.ru> (raw)
In-Reply-To: <CAAN8zSO4m7GA6+Nj5YGLd-vmMGOOJ=0dsudJtULeOt8hUJe-5w@mail.gmail.com>

On Wed, 2024-01-24 at 09:05 +0100, Lukáš Jiřiště via Libc-help wrote:
> Hello everyone,
> this is exciting as this is my first time ever using mailing list.
> I'm writing this, because I wanted to know, where to submit a minor
> typo in
> the GNU libc manual or whether there's a way I can fix it myself.
> Thank you all in advance. Have a nice day.

You can fix it yourself and send to a libc-alpha@sourceware.org ML. But
Glibc is very tough to contribute to because of lack of reviews for
patches, so patches often just hang in there for years. I've seen it
both from the side (you often see people ping over and over) and I have
myself a series of small fixes from 2019 or something that I was
pinging but to my knowledge by this day nobody reviewed it.

So unless you are motivated to ping over and over, I'd advice just fill
a bugreport. You can do that here
https://sourceware.org/bugzilla/enter_bug.cgi, chose "libc" as a
product.

  reply	other threads:[~2024-01-24  8:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24  8:05 Lukáš Jiřiště
2024-01-24  8:15 ` Konstantin Kharlamov [this message]
2024-01-24  8:19   ` Konstantin Kharlamov
2024-01-24 13:44     ` Carlos O'Donell
2024-01-24 13:46       ` Konstantin Kharlamov
2024-01-24 10:03 ` Szabolcs Nagy

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=7f7e6e9ad516d189fd073c3d078eec5d9d77643e.camel@yandex.ru \
    --to=hi-angel@yandex.ru \
    --cc=gymnazium.jiriste@gmail.com \
    --cc=libc-help@sourceware.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).