public inbox for xconq-cvs@sourceware.org
help / color / mirror / Atom feed
From: kingdon@sourceware.org
To: xconq-cvs@sources.redhat.com
Subject: xconq ./ChangeLog kernel/autotest.c
Date: Thu, 24 Jun 2004 05:24:00 -0000	[thread overview]
Message-ID: <20040624052457.30797.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/xconq
Module name:	xconq
Changes by:	kingdon@sourceware.org	2004-06-24 05:24:56

Modified files:
	.              : ChangeLog 
	kernel         : autotest.c 

Log message:
	* kernel/autotest.c (autotest): Disable test which is now failing
	(it would appear to be some kind of bug in the test code about
	whether we give tasks to the unit we set up).


             reply	other threads:[~2004-06-24  5:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-24  5:24 kingdon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-24  5:43 kingdon
2004-05-16 19:37 kingdon
2003-12-31  0:14 kingdon
2003-12-04  6:29 kingdon

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=20040624052457.30797.qmail@sourceware.org \
    --to=kingdon@sourceware.org \
    --cc=xconq-cvs@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).