From: Mark Kettenis <kettenis@chello.nl>
To: cgd@broadcom.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Recognize OpenBSD ELF
Date: Thu, 22 Jan 2004 22:44:00 -0000 [thread overview]
Message-ID: <200401222244.i0MMi3md043484@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <yov54qund41y.fsf@ldt-sj3-010.sj.broadcom.com> (cgd@broadcom.com)
From: cgd@broadcom.com
Date: 22 Jan 2004 14:14:17 -0800
At Thu, 22 Jan 2004 21:56:59 +0000 (UTC), "Mark Kettenis" wrote:
> The attached patch is pretty obvious, so I committed it.
i do wonder what the intended ordering of stuff in that function is.
looks like previous to this, things were in alphabetical order:
.note.ABI-tag
.note.netbsd.ident
.note.netbsdcore.procinfo
i dunno. probably not worth thinking about now, but maybe for
somebody who adds the next thing.
Well, I added .note.netbsd.ident and .note.netbsdcore.procinfo, so I
can say that the alphabetical order is completely unintentional. I'd
like to keep the .note.openbsd.ident close to .note.netbsd.ident since
they're almost identical.
Mark
prev parent reply other threads:[~2004-01-22 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 21:56 Mark Kettenis
[not found] ` <mailpost.1074808619.15112@news-sj1-1>
2004-01-22 22:14 ` cgd
2004-01-22 22:44 ` Mark Kettenis [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=200401222244.i0MMi3md043484@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=cgd@broadcom.com \
--cc=gdb-patches@sources.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