search for: upstreaming

Hello, I was unable to find clues to my problem in ?optim. Using the data and code below, I get an error ("system is exactly singular") when a particular line of code is left in, but have found that 'optim' works when I comment it out. The line of code in question is after the closeAllConnections() line of code and contains a call to "na.approx" from the zoo package.

Hello, I'm plotting two sets of data referenced to either the left or right y-axes. The first, water table depth (blue circles), is plotted on the left y-axis in reverse order (0 at the top) as this is more intuitive when thinking in terms of depth. The second is electrical conductance (a surrogate for salinity), and is referenced to the right y-axis. The data and plot commands follow

Oliver Schneider <gmane at assarbad.net> writes: >>> However, we have official git mirrors of most of the projects on >>> llvm.org, would using them instead of svnsync be an option for you? >> >> Well, if the authoritative source code control system for all the >> llvm projects is svn, I'd just as soon use svn as the tool at my end. > The git

Hello R list, This is a question for anyone who has used the by() command. I would like to perform a regression on a data frame by several factors. Using by() I think that I have able to perform this using the following: > lm.r <- by(master, list(Sectionf=Sectionf, startd=startd), function(x) lm (tot.c ~ starttime, data = x)) So that is, I would like to perform separate regressions for

On 2011-08-29 04:21, Kurt Lidl wrote: > While I agree bootstrapping a new mirror from scratch is time and > resource consuming, this can be largely avoided by making a seed > of the svn tree available. (Basically, I think that looks like > a compressed tar file of the svn repository.) Or, a svnadmin dump > of the repo could be made available for the adventurous. Having the same

Hi folks, From the roadmap for Xen 4.3 development, Xen 4.3 will use upstream QEMU (partially done). So I''d like to confirm the following questions. 1. Will Xen 4.3 really use upstream QEMU by default ? I have the question because so far the xen.git tree still uses qemu-xen-unstable by default. 2. If ''yes'' for 1st question, which QEMU upstream will be used in Xen

Processing commands for control at bugs.debian.org: > tags 496359 secuirity Unknown tag/s: secuirity. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental fixed-upstream l10n etch etch-ignore lenny lenny-ignore. Bug#496359: The possibility of attack with the help

This may be a nginx issue more than a mongrel one but I though folks in this list might be interested. Anyway, I have a mongrel_cluster with 2 front nginx workers as proxy. I recently replaced apache/mod_proxy for nginx, and I wasn''t aware of the 60 seconds default proxy_read_timeout so I went a head and tried to run a process via http GET. Normally because of the 60 seconds the GET I

...me lowering part. This mostly deals with emitting unwinding opcodes, as well as some small changes to the exception handling tables. Probably two patches. 4) Upstream setjmp support. This consists of two patches (one clang and one llvm). Any thoughts? Mandeep and I will start upstreaming shortly. Thanks, Sanjin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180717/afca7ec8/attachment.html>

Processing commands for control at bugs.debian.org: > tags 430778 + upstream Bug #430778 [xen-utils-common] xen-utils-common: NAT scripts not generic enough, and made for DHCP ? Added tag(s) upstream. > tags 430676 + upstream Bug #430676 [xen-utils-common] xen-utils-common: network-nat creates insecure nat POSTROUTING MASQUERADE ? Added tag(s) upstream. > tags 603366 + upstream Bug

Hi All, We did some testing for Xen-unstable tree with upstream QEMU. We covered basic guest booting up, power management, VT-d, SR-IOV features. We found 4 new bugs which only exist in upstream QEMU not in qemu-xen. We followed the below wiki page to use upstream QEMU. http://wiki.xen.org/wiki/QEMU_Upstream test tree: xen-unstable-tree.hg: C/S 26193 (about 20 days ago) qemu.git: commit

...t; It is true that downstream should be able continue to work easily based > of these official independent *git* repos ( i.e.: > http://llvm.org/git/llvm.git will continue to exist and be updated > without changing its history).  > However for individual developers that are continuously upstreaming their > work it does not seem sustainable, how do you pull from the individual > repos, do you work, commit as today, and push upstream? Today it is > possible with git-svn, while with the monorepo it won’t be possible. Speaking only for myself, the problem you suggest simply does not exi...

On Wed, Aug 17, 2011 at 01:47:02PM -0700, Benjamin Kramer wrote: > On 17.08.2011, at 11:36, Kurt Lidl <lidl at pix.net> wrote: > > > Why can't I mirror the whole tree? > > The original reason for this limitation was that complete checkouts > put a lot of stress on the server. While I agree bootstrapping a new mirror from scratch is time and resource consuming,

Hi, I was building LLVM with gcc 6.1.1 recently and it was spitting out some warnings relating to misleading indention that caught my eye. This wasn't a fresh build so I may have missed some. I've CC'ed the authors of the potentially misleading lines so they can decide what do about the warnings (if anything). I'm wondering if clang-format is making some inappropriate choices

Hello, this is Jesse with Webformix. We are managing an Asterisk installation for residential VOIP service, and we are having a problem where all inbound calls to DIDs which are assigned to us by our wholesaler but not yet assigned to a downstream customer get caught in a routing loop. ** For example: we get assigned DID block 1230-1239 and only 1230-1233 are given to our customers, then our

Hi! > Reassigning to Debian Xen team, since I that makes more sense. We > totally missed this on our (release) radar. > > And indeed, we're shipping the upstream completion file now. Adi, I see > how you're improving it, and I like it. I'm happy you like it... > So, we should probably ship this instead, but at the same time, the > right (tm) place to move this

I encountered a segfault when using lld to cross-compile for Windows (+MinGW) from Linux. The problem happens with objects built by gcc. The problem is that ObjFile::CreateRegular considers a PendingComdat to be valid (and later causes an illegal pointer dereference). The following patch fixes the crash: diff --git a/COFF/InputFiles.cpp b/COFF/InputFiles.cpp index 9e2345b0a..f47d612df 100644

I owe you a gala dinner at your favorite restaurant. Really. A few questions: Why did you 'git pull --rebase' when the branch was up-to-date? Is this just a safety habit? I don't understand the pushing upstream. Since we use Phabricator, isn't that the job of the person who commits the patch? Does git keep all my branches up-to-date with the origin? Say I come in tomorrow and

ei tuka imam edin pf conf obache pravi mnogo nomera, kato se pusne parvoto koeto e dropva paketi, timeoutva po serverite i t.n.. i speed-a e mnogo baven, vijte ako nqkoi moje da otkrie generalna greshka da reply :) vapreki che ne e freebsd-specific :P ne sym go pisal az a i ne sam mnogo mnogo zapoznat s pf zatova ako nqkoi moje da pomogne e dobre doshyl :) btw moje i neshto ot tia opcii kato set

Hi all, I talked to our oVirt developers who use CentOS for upstream development. And that's what makes their lives hard because it takes a long time before they can start using new features of libvirt. The latest released CentOS version is 7.2 with libvirt 1.2.17, which is pretty old. But even when CentOS 7.3 with libvirt 2.0.0 gets released, it will already be old since libvirt 2.5.0 is