From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Subject: Re: elfutils code names
Date: Tue, 21 Feb 2023 16:12:44 +0100 [thread overview]
Message-ID: <da8ea998e277a1a618774c209517b942a33da4b1.camel@klomp.org> (raw)
In-Reply-To: <fa6a559832ba37089eb3e4a30471ca7fe0c5245f.camel@klomp.org>
On Thu, 2023-02-16 at 13:37 +0100, Mark Wielaard wrote:
> Hi,
>
> On irc (#elfutils on libera.chat) we had a discussion about the
> elfutils code names. For some reason those are only in the irc channel
> topic. Which seems to mean not many people know about them. I could
> recover the following:
>
> 0.170 "DWARF4 1/2"
> 0.171 "DWARF5 split!"
> 0.172 "DWARF5 bugs split!"
> 0.173 "crash free"
> 0.174 "extended shnum"
> 0.176 "At your own RISC-V"
> 0.177 "What is your category, class and taxonomy?"
> 0.178 "All the build-id you can count!"
> 0.179 "All your packages are belong to us!"
> 0.180 "We got an L, we got an T, can we have a O?"
> 0.181 "Show me your ARMs"
> 0.182 "October Surprise!"
> 0.183 "100+ commits"
> 0.184 "negative results"
> 0.185 "oops, I did it again"
> 0.186 "Just In Time"
> 0.187 "no zero negatives"
> 0.188 "no section left behind"
>
> I believe some older versions also had code names, but I could not find
> them.
Found some more:
0.162 "hard hat"
0.163 "size matters"
0.164 "strip, no unstrip!"
0.165 "big DWARF & tiny ELF"
0.166 "bugs be gone!"
0.167 "disassemble this!"
0.168 "kthxbye"
So 0.169 is missing and I am not sure any version before 0.162 had a
code name. But if you remember differently please update/correct this
list.
Thanks,
Mark
next prev parent reply other threads:[~2023-02-21 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 12:37 Mark Wielaard
2023-02-21 15:12 ` Mark Wielaard [this message]
2023-02-23 8:35 ` Martin Liška
2023-02-23 10:06 ` Mark Wielaard
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=da8ea998e277a1a618774c209517b942a33da4b1.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@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).