From: Hans Reiser <reiser@namesys.com>
To: ReiserFS List <reiserfs-list@namesys.com>
Subject: status of reiser4 today
Date: Mon, 28 Jun 2004 11:12:24 -0700 [thread overview]
Message-ID: <40E05F88.3010700@namesys.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: [CVS] reiserfs --]
[-- Type: message/rfc822, Size: 2008 bytes --]
From: vs@thebsh.namesys.com
To: reiserfs-dev@namesys.com
Subject: [CVS] reiserfs
Date: Mon, 28 Jun 2004 20:04:13 ()
Message-ID: <20040628160413.12020.qmail@thebsh.namesys.com>
CVSROOT: /home/CVS
Module name: reiserfs
Repository: reiserfs/daily-reports/vs/
Changes by: vs@thebsh.namesys.com.(none) 04/06/28 20:04:13
Modified files:
reiserfs/daily-reports/vs/:
2004.06 1.20 -> 1.21
--------------[ DIFF ]----------------------------
Index: reiserfs/daily-reports/vs/2004.06
diff -u reiserfs/daily-reports/vs/2004.06:1.20 reiserfs/daily-reports/vs/2004.06:1.21
--- reiserfs/daily-reports/vs/2004.06:1.20 Fri Jun 25 21:24:19 2004
+++ reiserfs/daily-reports/vs/2004.06 Mon Jun 28 20:04:03 2004
@@ -207,3 +207,16 @@
upgrading to 2.6.7-mm2
documanting compile options
END 2004.06.25:21.24 Fri TOTAL=5:54
+BEG 2004.06.28:10.35 Mon
+ more stress tests before release
+ upgrading to 2.6.7-mm3
+END 2004.06.28:14.25 Mon TOTAL=3:50
+BEG 2004.06.28:15.35 Mon
+ completed all the preparations for release
+ checking various mount options
+ stressed reiser4 with multithread test:
+ reiser4 lockedup
+ trying to find whewre it deadlocked
+ nothing yet found because kgdb seems to be broken in 2.6.7-mm3
+ sigh, release is delayed
+END 2004.06.28:20.03 Mon TOTAL=4:28
--------------[ END DIFF ]------------------------
Log message:
vs's daily report for 28 june 2004
reply other threads:[~2004-06-28 18:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40E05F88.3010700@namesys.com \
--to=reiser@namesys.com \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.