similar to: for Yorkshir

Hi I'm working on a project which needs loop-attached metadata similar to the parallel metadata discussed in here. Currently I'm trying to make the metadata get through the optimisation passes unscathed. For loop passes, I've solved that by modifying the LPPassManager to check for metadata presence before and after runOnLoop, and restoring it if necessary (assuming the loop didn't

Hi I'm working on a project which needs loop-attached metadata similar to the parallel metadata discussed in here. Currently I'm trying to make the metadata get through the optimisation passes unscathed. For loop passes, I've solved that by modifying the LPPassManager to check for metadata presence before and after runOnLoop, and restoring it if necessary (assuming the loop didn't

Hi, I just completed a really big rsync described earlier. Ie about 13,945 directories transfered about 600GB of data. Of 13,945 directories, 13,9441 directories transfer with matching du -b sizes of the preimage to the size of the destination machine image. of the 4 remaining directories i found source vs destination in bytes --------- a) 20480 vs 34922496 b) 28672 vs

Patrick Laimbock wrote: > On 28-08-18 17:51, Alicia Smith wrote: >> >> I just joined this mailing list, so I apologize in advance if this >> topic has already been covered. >> >> Red Hat and Suse announced they are no longer supporting OpenLDAP in >> future releases. https://www.ostechnix.com/redhat-and-suse-announced-to- >>

Stephen John Smoogen wrote: > On Tue, 28 Aug 2018 at 14:56, mark <m.roth at 5-cent.us> wrote: > >> >> Patrick Laimbock wrote: >> >>> On 28-08-18 17:51, Alicia Smith wrote: >>> >>>> >>>> I just joined this mailing list, so I apologize in advance if this >>>> topic has already been covered. >>>>

Hello! I just joined this mailing list, so I apologize in advance if this topic has already been covered. Red Hat and Suse announced they are no longer supporting OpenLDAP in future releases. https://www.ostechnix.com/redhat-and-suse-announced-to- withdraw-support-for-openldap/ However, we mainly use CentOS and while it's a RH derivative, I wanted to find out what CentOS plans on doing in

> -----Original Message----- > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Mehdi > Amini via llvm-dev > Sent: Friday, July 29, 2016 10:02 AM > To: David Chisnall > Cc: llvm-dev at lists.llvm.org; Bruce Hoult > Subject: Re: [llvm-dev] [RFC] One or many git repositories? > > > > On Jul 29, 2016, at 2:19 AM, David Chisnall >

I don’t know what you mean by dealing with the merging, I don’t expect any difficulties, you need to elaborate. What I don’t see you addressing here is why this should be more of a problem in the monorepo case (as it was implied in the email I was answering to). Your answer made it sound like you thought the monorepo would solve all downstream problems ("I don't know what you mean… I

Hi Alicia, On 28-08-18 17:51, Alicia Smith wrote: > Hello! > > I just joined this mailing list, so I apologize in advance if this topic > has already been covered. > > Red Hat and Suse announced they are no longer supporting OpenLDAP in future > releases. > https://www.ostechnix.com/redhat-and-suse-announced-to- > withdraw-support-for-openldap/ > > However, we

On Tue, 28 Aug 2018 at 14:56, mark <m.roth at 5-cent.us> wrote: > > Patrick Laimbock wrote: > > On 28-08-18 17:51, Alicia Smith wrote: > >> > >> I just joined this mailing list, so I apologize in advance if this > >> topic has already been covered. > >> > >> Red Hat and Suse announced they are no longer supporting OpenLDAP in >

> On Jul 29, 2016, at 11:07 AM, Robinson, Paul <paul.robinson at sony.com> wrote: > > > >> -----Original Message----- >> From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org <mailto:llvm-dev-bounces at lists.llvm.org>] On Behalf Of Mehdi >> Amini via llvm-dev >> Sent: Friday, July 29, 2016 10:02 AM >> To: David Chisnall >> Cc:

On Thu, Jan 28, 2016 at 08:32:31AM -0800, Reid Kleckner via llvm-dev wrote: > I think Clang should continue to duplicate this information, the same way > we duplicate target datalayout strings. Other than that, sure, we can let > LLVM expand IR operations to libcalls. I don't immediately see a problem > with that. Note that a libcall doesn't necessarily mean using locks. With

Ein eingebundener Text mit undefiniertem Zeichensatz wurde abgetrennt. Name: nicht verf?gbar URL: <https://stat.ethz.ch/pipermail/r-help/attachments/20111023/ae046d6a/attachment.pl>

> 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

There has been a notice of a breach (see: CVE-2007-4752) as to some binary content upstream of CentOS. I do not address that matter here beyond stating that the CentOS team have responded to the matter, and will continue this review process: updated 22 Aug 2008 CentOS acknowledge CVE-2007-4752 and are reviewing our build and signing processes and hosts for signs of tampering subsequent

> On Sep 8, 2014, at 10:14 AM, Joerg Sonnenberger <joerg at britannica.bec.de> wrote: > > On Fri, Sep 05, 2014 at 09:23:34PM -0500, Richard Pennington wrote: >> Right now it only handles replacing a "-target foo" option >> with the options defined in the file foo in the resource/config >> directory, but I think it has potential for doing quite a bit

I'm setting up a server where I plan to use Jails to improve security I also have installed and am configuring ipfilter. Here are my questions: Because I'm using Jails, I will have to have multiple ip aliases on the network interface. I will use ipfilter to specify what can go to each of the addresses. (e.g., allow only incoming to port 80 on the jail running apache). Another

Warren Young wrote: > On Dec 9, 2015, at 11:55 AM, m.roth at 5-cent.us wrote: >> Matthew Miller wrote: >>> On Wed, Dec 09, 2015 at 01:05:15PM -0500, m.roth at 5-cent.us wrote: >>>>>> >>>> So, you're saying that end users need to go poke their noses into the >>>> development process >>> >>> If you want to go out of

This patchset allows the user to define and manage groups of domains. The patch augments the xm utility with the following commands: grp-create, grp-shutdown, grp-destroy, grp-reboot, grp-pause, grp-unpause, grp-save, grp-restore, grp-join, and grp-migrate. A goal during development of group operations was to match support for common domain operations: create, shutdown, destroy, reboot, pause,

Hi all, I''ve got a lot of video files on a zfs/cifs fileserver running SXCE. A little while ago the dual onboard NICs died and I had to replace them with a PCI 10/100 NIC. The system was fine for a couple of weeks but now the performance when viewing a video file from the cifs share is appauling. Videos stop and jerk with audio distortion. I have tried this from several client machines