From: Andrew Cagney <ac131313@cygnus.com>
To: Stephane Carrez <Stephane.Carrez@worldnet.fr>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: [RFA]: Fix TUI to build and run
Date: Tue, 17 Apr 2001 10:38:00 -0000 [thread overview]
Message-ID: <3ADC7305.F1CDA2A8@cygnus.com> (raw)
In-Reply-To: <3ABE08B0.9415328C@worldnet.fr>
I hope you realise this is a political and not a technical question.
Anyway, ignoring the politics ... :-)
The code contains a number extern additions in C files vis:
> diff -u -p -r1.5 tui.c
> --- tui.c 2000/12/15 01:01:51 1.5
> +++ tui.c 2001/03/25 16:55:30
...
> +extern Function *old_rl_getc_function;
Just keep in mind that MI/libgdb are ment to eventually replace all
those TUIDO macros.
Anyway, on to the politics, nuff sitting on the fence. Could I suggest:
o taging the GDB sources
before anything goes in
o checking out a separate
tree and then merging
/ committing the changes
incrementally.
For instance, the patch to zap
the __STDC__ stuff could
be separated out.
Beyond that, assume you've got a licence to kill.
Andrew
next prev parent reply other threads:[~2001-04-17 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-25 8:59 Stephane Carrez
2001-04-17 10:38 ` Andrew Cagney [this message]
2001-04-17 13:14 ` Stephane Carrez
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=3ADC7305.F1CDA2A8@cygnus.com \
--to=ac131313@cygnus.com \
--cc=Stephane.Carrez@worldnet.fr \
--cc=gdb-patches@sourceware.cygnus.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