aboutsummaryrefslogtreecommitdiffstats
path: root/REPORTING-BUGS
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@athlon.transmeta.com>2002-02-04 18:07:03 -0800
committerLinus Torvalds <torvalds@athlon.transmeta.com>2002-02-04 18:07:03 -0800
commit3544b3289d633721041f6d96d0efee8f79cd435b (patch)
treea5b201286eb880200347c923b115a19b97b7ff3d /REPORTING-BUGS
parent27c07b258df990ce981108198eca19b2512a202a (diff)
downloadhistory-3544b3289d633721041f6d96d0efee8f79cd435b.tar.gz
v2.4.3 -> v2.4.3.1
- Bob Tracy: Cyrix MTRR setup fix (don't make it twice as big as asked for) - Trond Myklebust: rpciod needs to be PF_MEMALLOC to avoid deadlocks on memory allocation when writing out NFS data under low memory conditions. Fix up BKL and RPC interactions. - Jeff Garzik: tulip network driver update - fix truncate to call down to the filesystem with the kernel lock. - David Mosberger: ia64 update - David Mosberger: simplify ELF program header generation. - Alan Cox: merge from -ac series - Jeff Garzik: make serial.c recognize modem devices properly
Diffstat (limited to 'REPORTING-BUGS')
-rw-r--r--REPORTING-BUGS7
1 files changed, 3 insertions, 4 deletions
diff --git a/REPORTING-BUGS b/REPORTING-BUGS
index 864e6f63073ef6..4160d1a4fced5f 100644
--- a/REPORTING-BUGS
+++ b/REPORTING-BUGS
@@ -25,10 +25,9 @@ list. Having a standardized bug report form makes it easier for you not to
overlook things, and easier for the developers to find the pieces of
information they're really interested in. Don't feel you have to follow it.
- First run the ver_linux script included as scripts/ver_linux or
-at <URL:ftp://ftp.sai.msu.su/pub/Linux/ver_linux> It checks out
-the version of some important subsystems. Run it with the command
-"sh scripts/ver_linux"
+ First run the ver_linux script included as scripts/ver_linux, which
+reports the version of some important subsystems. Run this script with
+the command "sh scripts/ver_linux".
Use that information to fill in all fields of the bug report form, and
post it to the mailing list with a subject of "PROBLEM: <one line