From 8e339d26a56cd5ce7fc3ed9a524808b6c1ce9a96 Mon Sep 17 00:00:00 2001 From: root Date: Wed, 18 Jan 2006 21:00:39 +0000 Subject: [PATCH] *** empty log message *** --- doc/rxvt.7.pod | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/doc/rxvt.7.pod b/doc/rxvt.7.pod index 4f047098..e2d2ef8a 100644 --- a/doc/rxvt.7.pod +++ b/doc/rxvt.7.pod @@ -161,20 +161,21 @@ daemon. =item I am using Debian GNU/Linux and have a problem... The Debian GNU/Linux package of rxvt-unicode in sarge contains large -patches that considerably change the behaviour of rxvt-unicode. Before -reporting a bug to the original rxvt-unicode author please download and -install the genuine version (L) -and try to reproduce the problem. If you cannot, chances are that the -problems are specific to Debian GNU/Linux, in which case it should be -reported via the Debian Bug Tracking System (use C to report -the bug). +patches that considerably change the behaviour of rxvt-unicode (but +unfortunately this notice has been removed). Before reporting a bug to +the original rxvt-unicode author please download and install the genuine +version (L) and try to reproduce +the problem. If you cannot, chances are that the problems are specific to +Debian GNU/Linux, in which case it should be reported via the Debian Bug +Tracking System (use C to report the bug). For other problems that also affect the Debian package, you can and probably should use the Debian BTS, too, because, after all, it's also a bug in the Debian version and it serves as a reminder for other users that might encounter the same issue. -=item I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? +=item I am maintaining rxvt-unicode for distribution/OS XXX, any +recommendation? You should build one binary with the default options. F now enables most useful options, and the trend goes to making them -- 2.34.1