Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Jiri Smid <smid@suse.cz>
Cc: gdb@sources.redhat.com, Jim Blandy <jimb@cygnus.com>
Subject: Re: Port to x86-64
Date: Wed, 21 Mar 2001 15:59:00 -0000	[thread overview]
Message-ID: <3AB8D41C.790A7B60@cygnus.com> (raw)
In-Reply-To: <s8v4rwosl3l.fsf@naga.suse.cz>

Jiri Smid wrote:
> 
>  Hello,
> 
> My name is Jiri Smid and I work for SuSE CR.
> SuSE works on porting Linux to new 64-bit AMD processors.
> I will work on port GDB.

This is good, really good - you've raised the flag early!

I can note/suggest the following:

	o	get that assignment in order

		Remember, GDB can only accept the code
		if the copyright of the work is all
		in order.  It is best to start working
		on this one now so that you don't get
		hit with it at the end.

		Part of this is ensuring that all
		people contributing to your GDB have
		a valid assignment in place.

	o	submit the configury mess early

		even if you don't have real code
		could I suggest thinking about
		separating this out so that
		you can get on with the real
		work.

		This also avoids the age old
		problem of things going into
		a tail spin while people agree
		on the correct name :-)

	o	Your code will need to use
		the multi-arch framework.

	o	You should watch out for
		the GNU coding standard.
		As they say, no pain, no gain :-)

I also wonder if you actually need a separate CVS repository and
couldn't just live on a branch of the official GDB repository?  It
should make merging a lot easier.

	Andrew


  parent 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
2001-03-21 15:59 ` Andrew Cagney [this message]
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=3AB8D41C.790A7B60@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@cygnus.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