Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix `testrun.log' output of manual `testrun's
Date: Sun, 21 Jan 2007 22:51:00 -0000	[thread overview]
Message-ID: <20070121225139.GA29708@nevyn.them.org> (raw)
In-Reply-To: <20070121222818.GA1835@host0.dyn.jankratochvil.net>

On Sun, Jan 21, 2007 at 11:28:18PM +0100, Jan Kratochvil wrote:
> Checked in.
> 
> I assume one does not need to post here about an unchanged approved commit.

Thanks.

It's not a big deal to me either way.  I don't know what other
maintainers think; I need to clean up the associated discussion from my
inbox, but it's not hard to do that from the gdb-cvs messages.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2007-01-21 22:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-13  9:08 Jan Kratochvil
2007-01-13 13:47 ` Mark Kettenis
2007-01-13 16:01 ` Daniel Jacobowitz
2007-01-14 15:34   ` Jan Kratochvil
2007-01-20 19:59     ` Daniel Jacobowitz
2007-01-21 22:28       ` Jan Kratochvil
2007-01-21 22:51         ` Daniel Jacobowitz [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=20070121225139.GA29708@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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