Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Multi-arch SKIP_SOLIB_RESOLVER
Date: Sun, 09 Nov 2003 17:41:00 -0000	[thread overview]
Message-ID: <200311091741.hA9Hf0cI015584@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <3FAE4371.6010405@gnu.org> (message from Andrew Cagney on Sun, 09 Nov 2003 08:38:57 -0500)

   Date: Sun, 09 Nov 2003 08:38:57 -0500
   From: Andrew Cagney <cagney@gnu.org>

   > I'm working on integrating some mostly SPARC-related patches from
   > David S. Miller.  There were also some general bits in his tree that
   > I'm going to check in on mainline.  Here's the first.

   You mean the stuff david posted here?

Some of it has been posted, some hasn't.  I explicitly asked David
about the copyright status, and he told me it was all written by
himself, and that is copyright assignment is still in place.

   > Committed as obvious (to mainline).

   It should be "m" or "M", and not "f".
   You'll also note that I've started deleting still lurking macros so 
   these conversions are no longer so obvious :-)

Hmm.  So the "f" conversions are no longer considered obvious?  The
problem with "m" and "M" is that they no longer define the macro that
we're replacing.  That means things become a bit more complicated.  Do
you want me to replace SKIP_SOLIB_RESOLVER with a truly multi-arched
function?

Mark


  reply	other threads:[~2003-11-09 17:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-09 12:07 Mark Kettenis
2003-11-09 13:39 ` Andrew Cagney
2003-11-09 17:41   ` Mark Kettenis [this message]
2003-11-09 20:38     ` Andrew Cagney
2003-11-10 21:49       ` Mark Kettenis

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=200311091741.hA9Hf0cI015584@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=cagney@gnu.org \
    --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