jeff@amsdsg.UUCP (Jeff Barr) (07/20/88)
I've just brought X11R2 up on our SUN 3/60's. After bringing everything down from uunet (at 1200 baud!), I mis-managed to lose the FIXES files. Could someone mail me the complete set of FIXES, or a pointer to them? In general, are more FIXES 'coming out', and if so, where are they posted?
RWS@ZERMATT.LCS.MIT.EDU (Robert Scheifler) (07/21/88)
In general, are more FIXES 'coming out', and if so, where are they posted? More fixes will `come out' when I don't have any higher priority items on my stack, and can take time to collect distributable fixes. Right now, many other things are higher priority. For example, I am much more interested in finishing getting correct backing-store/save-under code into our servers for R3 than I am in getting more fixes published. However, if people have problems that leave them dead in the water, and they tell us about it, we'll try within reason to get them going. 1. Fixes are available via anonymous ftp to expo.lcs.mit.edu (18.30.0.212), and usually decwrl.dec.com (128.45.0.1), in the directory /pub/X.V11R2/updates/, in files with prefix "fixes". Fixes get put there in batches at intervals only. Summary lines are in the README file. 2. For those without ftp access, individual fixes can be obtained by mail by sending a message to xstuff@expo.lcs.mit.edu. In the usual case, the message should have a subject line and no body, or a single-line body and no subject, in either case the line looking something like one of these: send fixes 1 2 3 4 5 6 7 8 9 10 send fixes 5 send fixes 8 13 4 To get a summary of fixes, make the line: index fixes If you need help, make the line: help Some mailers produce mail headers that are unusable for extracting return addresses. If you use such a mailer, you won't get any response. If you happen to know an explicit path, you can include a line like path foo%bar.bitnet@mitvma.mit.edu in the body of your message, and the daemon will use it. 3. Send bug reports to xbugs@expo.lcs.mit.edu. 4. Flames to /dev/null.