search for: lurch

I just created a new rails project "test". I then did "switchtower --apply-to ~/user/test test" I then moved into test and tried "rake restart" and got: kfelkins@lurch:~/user/test$ rake restart (in /home/kfelkins/user/test) rake aborted! Don''t know how to build task ''restart'' I see restart in deploy. Can restart be invoked from the command line? -Kelly -------------- next part -------------- An HTML attachment was scrubbed... URL: ht...

...h reads in bitcode, processes it, and re-emits it. We use this tool as a flexible way to integrate our tool into the Xcode, Android NDK, Chromium, and Linux build process. The problem we face is that bitcode changes, and when it does… future versions can read it, but past versions are left in the lurch. For instance LLVM 3.2svn can BitcodeReader from LLVM 3.1, but LLVM 3.1 can't BitcodeReader LLVM 3.2 (after r165739.) There was an element of this patch which would have helped enable bitcode compatibility (use-abs-operands), but alas it was not committed. This patch is essentially those mi...

...> > (world wide) understanding behind degaussing hard drives? > > > > I work for No Secrets Agency (NSA) Pte Ltd (fictitious company name > > used). My sales manager Edward Joseph Snowden (fictitious individual > > name used) had *promised* our customer Leave Me in the Lurch (S) Pte > > Ltd (fictitious company name used) that we would "DEGAUSS" their hard > > disks after the PC replacement and data migration exercise for 15 > > trillion PCs (fictitious number used). > > > > PC = Personal Computer, which includes desktops and lapt...

...s it. We use >> this tool as a flexible way to integrate our tool into the Xcode, Android NDK, >> Chromium, and Linux build process. >> >> The problem we face is that bitcode changes, and when it does… future versions >> can read it, but past versions are left in the lurch. For instance LLVM 3.2svn >> can BitcodeReader from LLVM 3.1, but LLVM 3.1 can't BitcodeReader LLVM 3.2 >> (after r165739.) There was an element of this patch which would have helped >> enable bitcode compatibility (use-abs-operands), but alas it was not committed. > &g...

...on which I want to ask is, what is the universal (world wide) understanding behind degaussing hard drives? I work for No Secrets Agency (NSA) Pte Ltd (fictitious company name used). My sales manager Edward Joseph Snowden (fictitious individual name used) had *promised* our customer Leave Me in the Lurch (S) Pte Ltd (fictitious company name used) that we would "DEGAUSS" their hard disks after the PC replacement and data migration exercise for 15 trillion PCs (fictitious number used). PC = Personal Computer, which includes desktops and laptops Last Friday, I had already reflected to my s...

...esses it, and re-emits it. We use > this tool as a flexible way to integrate our tool into the Xcode, Android NDK, > Chromium, and Linux build process. > > The problem we face is that bitcode changes, and when it does… future versions > can read it, but past versions are left in the lurch. For instance LLVM 3.2svn > can BitcodeReader from LLVM 3.1, but LLVM 3.1 can't BitcodeReader LLVM 3.2 > (after r165739.) There was an element of this patch which would have helped > enable bitcode compatibility (use-abs-operands), but alas it was not committed. can't you use a...

...ding behind degaussing hard drives? > >>> > >>> I work for No Secrets Agency (NSA) Pte Ltd (fictitious company name > >>> used). My sales manager Edward Joseph Snowden (fictitious individual > >>> name used) had *promised* our customer Leave Me in the Lurch (S) Pte > >>> Ltd (fictitious company name used) that we would "DEGAUSS" their hard > >>> disks after the PC replacement and data migration exercise for 15 > >>> trillion PCs (fictitious number used). > >>> > >>> PC = Personal Co...

On Nov 8, 2012, at 7:09 AM, Joe Abbey <jabbey at arxan.com> wrote: >>> The problem we face is that bitcode changes, and when it does… future versions >>> can read it, but past versions are left in the lurch. For instance LLVM 3.2svn >>> can BitcodeReader from LLVM 3.1, but LLVM 3.1 can't BitcodeReader LLVM 3.2 >>> (after r165739.) There was an element of this patch which would have helped >>> enable bitcode compatibility (use-abs-operands), but alas it was not committ...

FYI, There was an interest from a few people to create a formalization of Markdown as it is currently implemented. A W3C Community Group has been created for moving forward and exploring the idea and create a spec if necessary. A W3C Community Group [1] is a platform for discussing, publishing about a topic. You just need a free public W3C account [2] The community markdown group [3] has

...s, what is the universal > (world wide) understanding behind degaussing hard drives? > > I work for No Secrets Agency (NSA) Pte Ltd (fictitious company name > used). My sales manager Edward Joseph Snowden (fictitious individual > name used) had *promised* our customer Leave Me in the Lurch (S) Pte > Ltd (fictitious company name used) that we would "DEGAUSS" their hard > disks after the PC replacement and data migration exercise for 15 > trillion PCs (fictitious number used). > > PC = Personal Computer, which includes desktops and laptops > <snip> A l...

...orld wide) understanding behind degaussing hard drives? >>> >>> I work for No Secrets Agency (NSA) Pte Ltd (fictitious company name >>> used). My sales manager Edward Joseph Snowden (fictitious individual >>> name used) had *promised* our customer Leave Me in the Lurch (S) Pte >>> Ltd (fictitious company name used) that we would "DEGAUSS" their hard >>> disks after the PC replacement and data migration exercise for 15 >>> trillion PCs (fictitious number used). >>> >>> PC = Personal Computer, which includes de...

...39;s nice and snappy) 5. Easy Any thoughts? ~c Message: 2 Date: 26 Sep 2004 18:38:36 -0600 From: Steve Murphy <murf@e-tools.com> Subject: [Asterisk-Users] RE: What about a higher level configuration language To: Asterisk-Users@lists.digium.com Message-ID: <1096245516.20808.1400.camel@lurch.wyoming.e-tools.com> Content-Type: text/plain I see some discussion on "higher level config files" -- namely the extensions.conf I too, for several months, have been pondering the fact that priorities are like "assembly language", or the line numbers in old BASIC variants....

...hts. Their website is www. i've enjoyed everything you've posted. " Had to be a good actor to play so many weird parts so well. " Underneath this, Castor has orchestrated a forceful, chunky funk line, featuring a wah-wah guitar and high-speed Latin drumming. He leaves truth in the lurch. It's a saturnine ditty, penned by Ethel Waters' session pianist J.

...hts. Their website is www. i've enjoyed everything you've posted. " Had to be a good actor to play so many weird parts so well. " Underneath this, Castor has orchestrated a forceful, chunky funk line, featuring a wah-wah guitar and high-speed Latin drumming. He leaves truth in the lurch. It's a saturnine ditty, penned by Ethel Waters' session pianist J.

...tion definitions. Eswaran's fix is justified with this reason alone. The side effect of changing inliner behavior is irrelevant. > It has a functional impact and can be both necessary or impossible > to use to meet those functional requirements. This in turn leaves > programmers in a lurch if the functional requirements are ever in tension > with the optimizer requirements. Not sure what you mean. Performance conscious programmers use it all the time. > > We're also working really hard to get more widely deployed cross-module > optimization strategies, in part to fr...

...uot;Chris Lattner" <clattner at apple.com> wrote: > On Nov 8, 2012, at 7:09 AM, Joe Abbey <jabbey at arxan.com> wrote: >>>> The problem we face is that bitcode changes, and when it does… future versions >>>> can read it, but past versions are left in the lurch. For instance LLVM 3.2svn >>>> can BitcodeReader from LLVM 3.1, but LLVM 3.1 can't BitcodeReader LLVM 3.2 >>>> (after r165739.) There was an element of this patch which would have helped >>>> enable bitcode compatibility (use-abs-operands), but alas it was...

...;s fix is justified with this > reason alone. The side effect of changing inliner behavior is > irrelevant. > > > It has a functional impact and can be both necessary or impossible > > to use to meet those functional requirements. This in turn leaves > > programmers in a lurch if the functional requirements are ever in > > tension > > with the optimizer requirements. > > Not sure what you mean. Performance conscious programmers use it all > the time. > > > > > We're also working really hard to get more widely deployed > >...

Hi all, Recently there''s been discussion [1] in the Linux community about how filesystems should deal with rename(2), particularly in the case of a crash. ext4 was found to truncate files after a crash, that had been written with open("foo.tmp"), write(), close() and then rename("foo.tmp", "foo"). This is because ext4 uses delayed allocation and may not

...n alone. The side effect of changing inliner behavior is > > irrelevant. > > > > > It has a functional impact and can be both necessary or > > > impossible > > > to use to meet those functional requirements. This in turn leaves > > > programmers in a lurch if the functional requirements are ever in > > > tension > > > with the optimizer requirements. > > > > Not sure what you mean. Performance conscious programmers use it > > all > > the time. > > > > > > > > We're also working...

...ant. > > > > > > > > > It has a functional impact and can be both necessary or > > > > > impossible > > > > > to use to meet those functional requirements. This in turn > > > > > leaves > > > > > programmers in a lurch if the functional requirements are ever > > > > > in > > > > > tension > > > > > with the optimizer requirements. > > > > > > > > Not sure what you mean. Performance conscious programmers use it > > > > all > > &...