Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Chris Johns <cjohns@cybertec.com.au>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Using gdb with Borland's free compiler?
Date: Thu, 02 Oct 2003 03:44:00 -0000	[thread overview]
Message-ID: <3F7B9F28.4020103@cybertec.com.au> (raw)
In-Reply-To: <3F7AE95C.5020108@redhat.com>

Andrew Cagney wrote:
> 
> It might be prudent to not look at the existing patch too hard.  You'll 
> need to be able to sign a document stating that what you contribute is 
> your own work ....
> 

I do not know the Win32 API so makes this a little more effort than I can spare. I 
have asked about ths history of the patch on the MinGW list.

> Alternatively, you could use this list as an audit trail and explain 
> what needs to be done.

Not sure I understand what you mean. Is a list of the current patch changes ok ?

I was planing on breaking down the patch and sending them to the gdb patches list.

-- 
  Chris Johns, cjohns at cybertec . com . au


  reply	other threads:[~2003-10-02  3:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-28 23:24 Michael Elizabeth Chastain
2003-09-29 13:26 ` Andrew Cagney
2003-09-30 22:46   ` Chris Johns
2003-10-01 14:49     ` Andrew Cagney
2003-10-02  3:44       ` Chris Johns [this message]
2003-10-02 13:44         ` Christopher Faylor
2003-10-02 22:43           ` Chris Johns
2003-10-02 23:12             ` Andrew Cagney
2003-10-03  2:56               ` Chris Johns
2003-10-01  0:07   ` Christopher Faylor
2003-10-01  5:03     ` Eli Zaretskii
2003-10-01  5:58     ` Joel Brobecker
2003-10-01 13:10       ` Christopher Faylor
  -- strict thread matches above, loose matches on Subject: below --
2003-09-28 22:23 Vivi Orunitia

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=3F7B9F28.4020103@cybertec.com.au \
    --to=cjohns@cybertec.com.au \
    --cc=ac131313@redhat.com \
    --cc=gdb@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