From: Ben Elliston <bje@redhat.com>
To: sid@sources.redhat.com
Subject: Re: Testsuite improvement patch
Date: Sun, 18 Nov 2001 15:17:00 -0000 [thread overview]
Message-ID: <15381.19465.871435.857853@scooby.brisbane.redhat.com> (raw)
In-Reply-To: <15381.7613.416810.99371@scooby.brisbane.redhat.com>
Approved by fche.
Ben
WARNING: multiple messages have this Message-ID
From: Ben Elliston <bje@redhat.com>
To: sid@sources.redhat.com
Subject: Re: Testsuite improvement patch
Date: Mon, 10 Dec 2001 15:59:00 -0000 [thread overview]
Message-ID: <15381.19465.871435.857853@scooby.brisbane.redhat.com> (raw)
Message-ID: <20011210155900.ut8-lE9xE_pKK8wvaTkk_n1R0f4FHWpHEjG0B_Qaj0M@z> (raw)
In-Reply-To: <15381.7613.416810.99371@scooby.brisbane.redhat.com>
Approved by fche.
Ben
next prev parent reply other threads:[~2001-12-10 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 14:42 Ben Elliston
2001-11-18 15:17 ` Ben Elliston [this message]
2001-12-10 15:59 ` Ben Elliston
2001-12-10 15:48 ` Ben Elliston
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=15381.19465.871435.857853@scooby.brisbane.redhat.com \
--to=bje@redhat.com \
--cc=sid@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).