public inbox for debugedit@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: debugedit@sourceware.org
Subject: [Bug find-debuginfo.sh/27640] find-debuginfo.sh or find-debuginfo?
Date: Thu, 06 May 2021 00:33:37 +0000	[thread overview]
Message-ID: <bug-27640-13298-LhNSZ8dyll@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27640-13298@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27640

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at klomp dot org,
                   |                            |pmatilai at redhat dot com

--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
It would be nice to rename it to simply find-debuginfo. But this might have
some backwards compatibility issues for rpm and old spec files which might rely
on the exact name. This might not be too strong an objection to renaming it
though. Up till now this was an internal detail of rpm.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2021-05-06  0:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24  6:34 [Bug find-debuginfo.sh/27640] New: " doko at debian dot org
2021-05-06  0:33 ` mark at klomp dot org [this message]
2021-05-06  9:52 ` [Bug find-debuginfo.sh/27640] " pmatilai at redhat dot com
2021-05-18 17:26 ` [Bug find-debuginfo/27640] " mark at klomp dot org
2021-06-14 10:26 ` pmatilai at redhat dot com
2021-06-14 10:35 ` ldv at sourceware dot org
2021-06-17 16:59 ` mark at klomp dot org
2021-06-18  7:03 ` pmatilai at redhat dot com

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=bug-27640-13298-LhNSZ8dyll@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=debugedit@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).