From: James Ingham <jingham@cygnus.com>
To: Jonathan Larmour <jlarmour@redhat.co.uk>
Cc: James Ingham <jingham@cygnus.com>,
Andrew Cagney <ac131313@cygnus.com>,
insight@sourceware.cygnus.com, gdb-patches@sourceware.cygnus.com
Subject: Re: Insight remote output doesn't output to console window immediately
Date: Fri, 14 Apr 2000 08:53:00 -0000 [thread overview]
Message-ID: <14583.16305.343648.795283@leda.cygnus.com> (raw)
In-Reply-To: <38F6873A.8284A61B@redhat.co.uk>
Jonathan,
> James Ingham wrote:
> >
> > Okay, check this in.
>
> Trunk, branch or both?
Both. Maybe add a FIXME to the comment, since I often grep for FIXME
when I am trying to figure out what I should do next (though as I
said, this one is already on the short list.)
>
> > As for the Changelog-gdbtk's. They should be changed to just
> > ChangeLog - the gdbtk is historic; the C-code files used to live at
> > the top level, but since Insight couldn't be included in the FSF gdb
> > releases, we had to have separate ChangeLogs...
>
> Would you like me to rename those two then? Obviously not forgetting to
> remove all the change-log-default-name emacs variables. That would be trunk
> only of course.
That would be lovely, thanks.
Jim
next prev parent reply other threads:[~2000-04-14 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-13 14:46 Jonathan Larmour
2000-04-13 16:53 ` Andrew Cagney
2000-04-13 16:56 ` James Ingham
2000-04-13 18:36 ` Jonathan Larmour
2000-04-13 18:54 ` James Ingham
2000-04-13 19:49 ` Jonathan Larmour
2000-04-14 8:53 ` James Ingham [this message]
2000-04-17 13:07 ` Jonathan Larmour
2000-04-17 13:15 ` James Ingham
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=14583.16305.343648.795283@leda.cygnus.com \
--to=jingham@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=jlarmour@redhat.co.uk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).