public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adam Sampson <ats@offog.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH v2 0/2] ldconfig: Ignore all GDB extension files
Date: Wed, 5 Jun 2024 10:49:35 +0100	[thread overview]
Message-ID: <ZmA0r4K-vRIlnlyN@cartman.at.offog.org> (raw)
In-Reply-To: <20240506171633.30008-1-ats@offog.org>

Ping - any further changes needed for these?

On Mon, May 06, 2024 at 06:16:31PM +0100, Adam Sampson wrote:
> ldconfig already ignores files with the -gdb.py suffix, but GDB also
> looks for -gdb.gdb and -gdb.scm files. These aren't as widely used, but
> libguile at least comes with a -gdb.scm file.
> 
> These patches make ldconfig ignore all three types of file.
> 
> Changes from v1:
> * Reuse ldconfig's endswithn function (suggested by Florian Weimer).
>   I didn't spot any other places that could use this directly, although
>   there are several tests that have implementations of startswith.
> 
> Adam Sampson (2):
>   ldconfig: Move endswithn into a new header file
>   ldconfig: Ignore all GDB extension files

On Patchwork:
https://patchwork.sourceware.org/project/glibc/patch/20240506171633.30008-2-ats@offog.org/
https://patchwork.sourceware.org/project/glibc/patch/20240506171633.30008-3-ats@offog.org/

Thanks,

-- 
Adam Sampson <ats@offog.org>                         <http://offog.org/>

      parent reply	other threads:[~2024-06-05  9:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 17:16 Adam Sampson
2024-05-06 17:16 ` [PATCH v2 1/2] ldconfig: Move endswithn into a new header file Adam Sampson
2024-05-06 17:16 ` [PATCH v2 2/2] ldconfig: Ignore all GDB extension files Adam Sampson
2024-06-05  9:49 ` Adam Sampson [this message]

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=ZmA0r4K-vRIlnlyN@cartman.at.offog.org \
    --to=ats@offog.org \
    --cc=libc-alpha@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).