From: Keith Seitz <keiths@cygnus.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Insight List <insight@sourceware.cygnus.com>
Subject: Re: Patch: Fix .gdbtkinit reading
Date: Wed, 22 Aug 2001 15:26:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0108221525420.22387-100000@makita.cygnus.com> (raw)
In-Reply-To: <87wv3v6a60.fsf@creche.redhat.com>
On 22 Aug 2001, Tom Tromey wrote:
> Tom> I found this while trying to use a saved session. I tested the
> Tom> appended patch on that session. Ok to commit?
>
> Keith> Looks pretty innocent to me.
>
> I took this as an `ok' and I've committed the patch.
Yes, indeed. I should learn to be more black-and-white on checkins.
Thanks.
Keith
prev parent reply other threads:[~2001-08-22 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 14:39 Tom Tromey
2001-08-22 11:38 ` Keith Seitz
2001-08-22 11:43 ` Tom Tromey
2001-08-22 12:01 ` Keith Seitz
2001-08-22 14:11 ` Tom Tromey
2001-08-22 15:26 ` Keith Seitz [this message]
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=Pine.GSO.4.33.0108221525420.22387-100000@makita.cygnus.com \
--to=keiths@cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).