Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: jtc@redback.com
Cc: Jiri Smid <smid@suse.cz>, gdb@sources.redhat.com
Subject: Re: Port to x86-64
Date: Wed, 21 Mar 2001 15:59:00 -0000	[thread overview]
Message-ID: <u866h3k6tq.fsf@gromit.rhein-neckar.de> (raw)
In-Reply-To: <5m66h47y9k.fsf@jtc.redback.com>

jtc@redback.com (J.T. Conklin) writes:

> >>>>> "Jiri" == Jiri Smid <smid@suse.cz> writes:
> Jiri> My name is Jiri Smid and I work for SuSE CR.
> Jiri> SuSE works on porting Linux to new 64-bit AMD processors.
> Jiri> I will work on port GDB.
> 
> Is there anything that you need from us?  

I think at this point not really, I'll guess that we'll contact you as
soon as we encounter specific problems.  

Btw. We will setup a separate CVS archive and use that for everything
and then merge to the mainline back.  Information about the x86-64
port is available at http://www.x86-64.org .

> It's better to keep the GDB maintainers informed as much as possible
> when it comes to a new port, as it will make integration of the port
> into the master sources considerably easier.  I believe Andrew has a
> short list of requirements a new ports must adhere to before a port 
> can be integrated that you might want to familiarize yourself with
> before getting too far along.

If there's such a list, then please point us to it.  If there's any
other guidance you can give Jiri, that's warmly welcome.

Thanks,
Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj


  reply	other threads:[~2001-03-21 15:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21 15:59 Jiri Smid
2001-03-21 15:59 ` J.T. Conklin
2001-03-21 15:59   ` Andreas Jaeger [this message]
2001-03-21 15:59 ` Andrew Cagney
2001-04-03  1:42 Jiri Smid
2001-04-06 12:23 ` Andrew Cagney
2001-04-06 15:02   ` Andreas Jaeger

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=u866h3k6tq.fsf@gromit.rhein-neckar.de \
    --to=aj@suse.de \
    --cc=gdb@sources.redhat.com \
    --cc=jtc@redback.com \
    --cc=smid@suse.cz \
    /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