similar to: Bug list summary (automatic post)

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

R-devel Digest Monday, September 24 2001 Volume 01 : Number 314 In this issue: [Rd] R 1.3.1 fails 'make check' on arm in the Bessel example (PR#1097) [Rd] Bug list summary (automatic post) [Rd] (PR#1089) Can be closed See the end of the digest for information about r-devel-digest ---------------------------------------------------------------------- Date: Fri, 21

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

In looking over the bugs list, it seems to me that most of them are things we can no longer do anything about, because they are on old versions or broken systems or were features or .... There are now so many they obscure the bugs needing attention. I am about the remove the following. If anyone thinks they are still relevant, could you please send a follow-up to R-bugs with details under 1.2.0

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

************* Content Filter Notification ************** The following mail was blocked since it contains sensitive content. Source mailbox: <s-luppescu at uchicago.edu> Destination mailbox(es): <r-help at stat.math.ethz.ch> Policy: Dirty Words(shit) Action: Quarantine Recipient, Content filter has detected a sensitive e-mail. ******************* End of message *******************

Problem: neither fg or bg nor color work properly in dotchart. version: R-1.7.1 for windows code which shows the errors: x <- matrix(rnorm(16),ncol=2,dimnames=list(paste("a",1:8,sep=""),c("before","afte r"))) dotchart(x,fg="blue",bg="lightgrey") dotchart(x,color=c("red","blue")) Dr Ian J Wilson Lecturer in

I'm not sure this list is the right place for this thing. I noticed some erratic behaviour in sammon(). Running sammon on two nearly identical sets of data results in very different results. Below is an example. I create an initial configuration with cmdscale() and store it into 'vec1'. I write this to file, and read it back in again to 'vec2'. According to cor() on the three

https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=512 ------- Additional Comments From yi_he@pmc-sierra.com 2006-10-23 09:09 MET ------- I've met the problem in the 2.4 kernel as well, and I modified the source linux/net/ipv4/netfilter/ip_nat_pptp.c like this: in function pptp_outbound_pkt(): ...... switch (msg = ntohs(ctlh->messageType)) { case

https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=448 laforge@netfilter.org changed: What |Removed |Added ---------------------------------------------------------------------------- Component|ip_conntrack |nf_conntrack ------- Additional Comments From laforge@netfilter.org 2006-02-14 09:05 MET ------- ipv6 conntrack is

Hello David, Thanks for your example. Is that means that DAG pattern is consist of LLVM IR instruction?? I met an example [(set CPURegs:$dst, (OpNode CPURegs:$b, CPURegs:$c))] of MipsInstrInfo.td, but I can't find correspond LLVM IR instruction of "set" in "LLVM Language Reference Manual". Is that correspond to $dst = op $b, $c?? Would you mind to tell me whether there is

Hi, I am using the following R version: > R version 2.4.1 (2006-12-18) > Copyright (C) 2006 The R Foundation for Statistical Computing > ISBN 3-900051-07-0 I believe I found a bug in the 'hist' function, when 'probability=TRUE'. I looked in the archives and I came across problems with the 'hist' functions (e.g., bug PR# 944, posted in 2001), however, a