search for: firehose

...y customizable. I've added a couple of views to the main menu: - My activity: https://reviews.llvm.org/home/menu/view/133/ is (active reviews, recent commits) x (i'm reviewer, i'm author). Only visible when logged in. - All commits: https://reviews.llvm.org/home/menu/view/135/ is the firehose I'd like to make "my activity" the default view for logged-in users, and "all commits" the default when logged out. (This is done by removing "home" from the menu). These aren't optimal for any particular person (e.g. I'd like to see all clangd changes),...

...worked really well. I still get all the ISO C++ mailings, and the signal to noise ratio is pretty good in this regard. > > +1 for an “llvm-project” list that everyone involved in any llvm subproject is encouraged to sign up for. Another +1 from me. The llvm-dev and cfe-dev lists are both firehoses and a lot of people on the periphery of the community don’t subscribe to them for this reason (which is not a negative, it’s a sign of a healthy and active project). A lower-traffic list for everyone in the community would be very useful. David -------------- next part -------------- A non-text...

...rails but to no avail, if I have 10 windows open and refresh all at once, several windows will produce that error. MS suggests (http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B272358): Use a server-side or client-side cursor other than the forward-only and read-only (often called a firehose) cursor. Anyone know how to do this? Help is appreciated. Thanks, Nazar -- Posted via http://www.ruby-forum.com/.

...tatement. As of today you can send a diff to the mailing list, I don’t see how lower the bar can be. Really? You don’t see that hitting the web UI buttons that construct a pull request are lower than finding a mailing list to post to, subscribing, preparing a patch, emailing it, filtering out the firehose of unrelated things? I migrated another open source project to GitHub last year. After several years of accepting patches via a mailing list and receiving no patches as a result, I immediately started getting patches sent as pull requests. I simply cannot overstate how much easier this mechanism...

...ews to the main menu: >> - My activity: https://reviews.llvm.org/home/menu/view/133/ is (active >> reviews, recent commits) x (i'm reviewer, i'm author). Only visible when >> logged in. >> - All commits: https://reviews.llvm.org/home/menu/view/135/ is the >> firehose >> >> I'd like to make "my activity" the default view for logged-in users, and >> "all commits" the default when logged out. (This is done by removing "home" >> from the menu). >> >> These aren't optimal for any particular pe...

Xiph.Org announces its first documentary video production: "A Digital Media Primer for Geeks" http://www.xiph.org/video/ "A Digital Media Primer For Geeks" is the first video from Xiph.Org, presenting the technical foundations of modern digital media via a half-hour firehose of information. Christopher "Monty" Montgomery, Red Hat engineer and founder of the Xiph.Org project, guides this tour through the foundations of digital video. The program offers a brief history of digital media, a quick summary of the sampling theorem, and myriad details of low-level au...

Dom0 is Wheezy 64 bit with kernel 3.2.0-1-amd64 version 3.2.4-1, xen from xen-unstable.hg changeset 24858:a88ba599add1 plus these patch for not fail build: http://xen.1045712.n5.nabble.com/PATCH-0-of-2-rename-libxl-yajl-gen-alloc-td5469362.html And also this change for lib patch modified with multiarch support: vi config/StdGNU.mk LIBLEAFDIR_x86_64 ?= lib DomUs PV working, domUs with

...vity has died off (i.e. they're 'stuck'). Obviously this is something that I can just go ahead and do, but I'd appreciate feedback on whether this would be useful, as well as the specifics of my proposed approach. I'd argue such a listing does provide value above and beyond the firehose of {llvm,cfe}-commits, as the two mentioned categories are not easily discoverable. How to select the patches to include? I'm going to rule out manual curation - LLVM Weekly is already a large time commitment and I'm not convinced trawling llvm-commits is the way to about this even if time...

...t;> On 6 Jul 2016, at 05:32, Chris Lattner via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> +1 for an “llvm-project” list that everyone involved in any llvm subproject is encouraged to sign up for. >> >> Another +1 from me. The llvm-dev and cfe-dev lists are both firehoses and a lot of people on the periphery of the community don’t subscribe to them for this reason (which is not a negative, it’s a sign of a healthy and active project). A lower-traffic list for everyone in the community would be very useful. > > I'm not against the idea, never have been,...

Hi guys.. I new on this list :-) I have a Icecast2 working on FreeBSD sending theora video from .avi, i writing manual here http://angelvg.blogspot.com/2009/07/freebsd-icecast2-theora.html I try to put relay from radio stations on internet from WWW.RAUTEMUSIK.FM, this radio station have this data: IP 205.188.215.228 PORT 8034 This work good <relay>

I am reading the comprehensive on-line documentation about msm. The positive side is that it seems it has been designed for biomedical statistics, like Clinical Trials. The bad side is that it does not seem to model observations sequences that are not independent but instead are autocorrelated, as it is my case. I did not find any mention to correlated observations therefore I assume the authors

...own. I think that if announcements and release info were made in a dedicated twitter channel, people could leverage twitter for real-time or "near-line" consumption of important information. If many types of tweets are comingled in one account, the value of the channel is diluted by the firehose of meaningless chatter. Have I just overlooked the appropriate digium twitter account? -Karl -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090127/b97115a9/attachment.htm

...e, move tests to target-specific directories, add an include file. B. real problems, like an assert in the code, seg fault, bad test results. C. hard problems, like bad codegen affecting self-hosting, intermittent failures in test-suite or self-hosted clang. Problems of type A. tend to show by the firehose on ARM, while they're a lot less common on x86_64 bots just because people develop on x86_64. Problems B. and C. and equally common on all platforms due to the complexity of the compiler. Problems of type B. should have same behaviour in all platforms. If the bots are fast enough (either fast...

Hi, A most peculiar and vexing problem for you all. I hope I have been verbose enough without being a firehose ;) The set up: I have a channel bank, using the r1t1 rhino driver with a rhino T1 card (the channel bank itself is a very legacy piece of equipment)- this supplies FXS for all the house phones. Also, a Wildcard TDM400P, using the wctdm module with 1 FXO module, this supplies FXO to the upstream te...

...they're 'stuck'). > > Obviously this is something that I can just go ahead and do, but I'd > appreciate feedback on whether this would be useful, as well as the specifics > of my proposed approach. I'd argue such a listing does provide value above and > beyond the firehose of {llvm,cfe}-commits, as the two mentioned categories are > not easily discoverable. > > How to select the patches to include? I'm going to rule out manual curation - > LLVM Weekly is already a large time commitment and I'm not convinced trawling > llvm-commits is the way to...

> On Jul 29, 2016, at 2:19 AM, David Chisnall <david.chisnall at cl.cam.ac.uk> wrote: > > On 29 Jul 2016, at 05:11, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> What I meant by “different problem" is that “downstream users” for instance don’t need to commit, that makes their problem/workflow quite different from an upstream developer

For ISO C++ we long ago created an 'all' list for topics that were organisational and not technically specific to an aspect of the Standard such as Library, or Core, or Extensions, etc.. For the most part I think that since the early 1990s when these lists started, the 'all' reflector/distribution-list has worked really well. I still get all the ISO C++ mailings, and the signal

Hai, In addition to Rowlands question. Can you run this script and post it to the list also. It gives a complete overview of what your running. Its basicly what Rowland asked, but with a few extra things. https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh And the output of: kinit Administrator klist klist -ket /var/lib/samba/private/secrets.keytab

...include >> file. >> B. real problems, like an assert in the code, seg fault, bad test results. >> C. hard problems, like bad codegen affecting self-hosting, >> intermittent failures in test-suite or self-hosted clang. >> >> Problems of type A. tend to show by the firehose on ARM, while they're >> a lot less common on x86_64 bots just because people develop on >> x86_64. > > > They show up often enough cross-OS and build config too (-Asserts, Windows, > Darwin, etc). > >> >> Problems B. and C. and equally common on all platf...

Thanks in advance. here's the total firehose drink. I've obscured host, domain, subnet. Hope that will still work for you. Don't want all the info publicized. klist -ket /var/lib/samba/private/secrets.keytab!! there is no /var/lib/samba/private/secrets.keytab klist -ket /etc/krb5.keytab KVNO Timestamp           Principal ---- -----...