public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: Add -j/--display-section option to readelf
Date: Tue, 18 Jun 2024 10:43:49 +0200	[thread overview]
Message-ID: <3b09a77d-5623-4073-9414-c1f0e8f6b97e@suse.com> (raw)
In-Reply-To: <2504a9c2-a666-4907-b9b2-52f6286d8e4c@redhat.com>

On 18.06.2024 10:34, Nick Clifton wrote:
> Hi Jan,
>> I notice this commit added use of a file with a .0 extension (the file
>> itself was added by a separate, earlier one). While of course in principle
>> any extension may be used for testcase expectations, I find this a little
>> odd (and, likely irrelevant here, it gets in the way of some of my
>> scripting). Would you mind if I renamed the file to display-section-0.r
>> (and the other one perhaps to display-section-rel.r for consistency)?
> 
> Not at all, please do.

Thanks.

> On a totally unrelated topic, there is something that I have been meaning
> to ask you.  Would you be interesting in becoming a co-chief maintainer of
> the GNU Binutils ?
> 
> I ask because Alan is retiring, and I am hoping to something similar in a
> few years time.  So it would be good to have someone with both the energy
> and the knowledge to take over running the Binutils project.  What do you
> think ?

Well. I certainly much appreciate the consideration. Yet "in a few years
time" perhaps applies to me as well, so trying to find someone a little
younger than (apparently) the two of us may be better. Plus I'm not sure
I could accommodate this, both time and infrastructure wise (albeit at
least the latter could likely be sorted, with some effort).

Jan

      reply	other threads:[~2024-06-18  8:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18  8:21 Jan Beulich
2024-06-18  8:34 ` Nick Clifton
2024-06-18  8:43   ` Jan Beulich [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=3b09a77d-5623-4073-9414-c1f0e8f6b97e@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).