search for: botches

Sorry, I botched a commit and broke the build. I've just committed a fix. So expect to see some buildbot churning. -Dave

On Monday 15 February 2010 11:54:25 Óscar Fuentes wrote: > David Greene <dag at cray.com> writes: > > Sorry, I botched a commit and broke the build. I've just committed a > > fix. > > > > So expect to see some buildbot churning. > > Don't hurry. A buildbot already decided that I am the only culprit of > the breakage. :-/ Hmm...given that

I think I botched syslinux-6.04-pre3. There are two fundamental problems with the build: a) The selection of what pieces of the library gets included in the core is done manually whereas it really should be automatic; b) The build doesn't fail if there are unresolved dependencies between the libraries and the core. I will fix these. (b) is IMO fundamental to avoid this error in the

David Greene <dag at cray.com> writes: > Sorry, I botched a commit and broke the build. I've just committed a fix. > > So expect to see some buildbot churning. Don't hurry. A buildbot already decided that I am the only culprit of the breakage. :-/ And some people pretend to use computer technology to pinpoint terrorists...

On Feb 15, 2010, at 10:00 AM, David Greene wrote: > On Monday 15 February 2010 11:54:25 Óscar Fuentes wrote: >> David Greene <dag at cray.com> writes: >>> Sorry, I botched a commit and broke the build. I've just committed a >>> fix. >>> >>> So expect to see some buildbot churning. >> >> Don't hurry. A buildbot already

On Feb 15, 2010, at 12:53 PM, Chris Lattner wrote: > > On Feb 15, 2010, at 10:00 AM, David Greene wrote: > >> On Monday 15 February 2010 11:54:25 Óscar Fuentes wrote: >>> David Greene <dag at cray.com> writes: >>>> Sorry, I botched a commit and broke the build. I've just committed a >>>> fix. >>>> >>>> So expect

On Monday 15 February 2010 14:59:19 Chris Lattner wrote: > On Feb 15, 2010, at 12:53 PM, Chris Lattner wrote: > > On Feb 15, 2010, at 10:00 AM, David Greene wrote: > >> On Monday 15 February 2010 11:54:25 Óscar Fuentes wrote: > >>> David Greene <dag at cray.com> writes: > >>>> Sorry, I botched a commit and broke the build. I've just committed

On Mon, 2019-02-11 at 12:15 -0800, H. Peter Anvin via Syslinux wrote: > > > I think I botched syslinux-6.04-pre3. There are two fundamental > problems with the build: > > a) The selection of what pieces of the library gets included in the core > is done manually whereas it really should be automatic; > > b) The build doesn't fail if there are unresolved

On February 11, 2019 12:29:41 PM PST, Joakim Tjernlund <Joakim.Tjernlund at infinera.com> wrote: >On Mon, 2019-02-11 at 12:15 -0800, H. Peter Anvin via Syslinux wrote: >> >> >> I think I botched syslinux-6.04-pre3. There are two fundamental >> problems with the build: >> >> a) The selection of what pieces of the library gets included in the >core

https://bugzilla.mindrot.org/show_bug.cgi?id=1414 Summary: Botched getpwuid usage on Mac OS X Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: Other OS/Version: Mac OS X Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: bitbucket at mindrot.org

I just built up a server running CentOS 4.3, and trying to boot from a 3Ware 9550SX-16ML, 16 port card. This system has 9x500GB drives, AMD Opteron, Tyan K8SD mobo and 1 GB of ram. I downloaded the latest (9.3.0.4) driver from 3Ware, and after a couple of botched attempts, I got CentOS installed. In my two botched attempts, the problem was X hanging during the formatting of the drives, so I

Unless others find this objectionable, it would be nice to see the grammar for metadata instruction attachment in the http://llvm.org/docs/LangRef.html#metadata section. The grammar you gave earlier seems to work. Garrison On Feb 15, 2010, at 16:17, David Greene wrote: > On Monday 15 February 2010 15:08:22 Chris Lattner wrote: >> On Feb 15, 2010, at 1:04 PM, David Greene wrote:

I have a 6.5 box that failed to boot after a kernel update. The reason is the first arg on the kernel line: title CentOS (2.6.32-431.11.2.el6.x86_64) root (hd0,0) kernel /tboot.gz ro root=/dev/mapper/vol0-lvol1 intel_iommu=on rd_NO_LUKS LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_NO_DM KEYBOARDTYPE=pc KEYTABLE=us rd_LVM_LV=vol0/lv ol3

hello everyone! i have a problem checking out the icecast cvs. the checkout stalls after pulling timing/timing.h (no matter which module, they all seem to depend on it). i have to kill it after a while. am i doing anything wrong, or is your cvs botched ? for now, i'm using a nightly snapshot, but i can't find ices2 in it, so i tried to pull cvs. btw, the chroot feature is cool. i

On Monday 15 February 2010 15:08:22 Chris Lattner wrote: > On Feb 15, 2010, at 1:04 PM, David Greene wrote: > >> FWIW, this is because you broke the encoding of an instruction in your > >> patch. This is incorrect: > >> > >> +def MOVNTDQ_64mr : PSI<0xE7, MRMDestMem, (outs), (ins f128mem:$dst, > >> VR128:$src), +

On Monday 15 February 2010 15:27:34 Chris Lattner wrote: > On Feb 15, 2010, at 1:17 PM, David Greene wrote: > > On Monday 15 February 2010 15:08:22 Chris Lattner wrote: > >> On Feb 15, 2010, at 1:04 PM, David Greene wrote: > >>>> FWIW, this is because you broke the encoding of an instruction in your > >>>> patch. This is incorrect: >

On Feb 15, 2010, at 1:04 PM, David Greene wrote: >> FWIW, this is because you broke the encoding of an instruction in your >> patch. This is incorrect: >> >> +def MOVNTDQ_64mr : PSI<0xE7, MRMDestMem, (outs), (ins f128mem:$dst, >> VR128:$src), + "movntdq\t{$src, $dst|$dst, $src}", >> + [(alignednontemporalstore

Naturally, you tinker around with stuff long enough and you break it. I am running Samba 2.2.2 on a Corel linux box and am attempting to connect to a share on a windows XP system. At one point, this was working fine. Then I spent time trying to reconfigure my kernel so that I could attach a floppy tape drive and now I can connect with smbclient to the share, but I cannot with smbmount. I have

On 17 May 2016 at 20:04, Justin Bogner via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> Note that this would also fire when a commit referring to a PR gets >> reverted (assuming the reverting commit doesn't botch the commit >> message), etc., which is super useful for those following along on the >> bug's cc list. > > +1. This would be a very useful

On Feb 15, 2010, at 1:17 PM, David Greene wrote: > On Monday 15 February 2010 15:08:22 Chris Lattner wrote: >> On Feb 15, 2010, at 1:04 PM, David Greene wrote: >>>> FWIW, this is because you broke the encoding of an instruction in your >>>> patch. This is incorrect: >>>> >>>> +def MOVNTDQ_64mr : PSI<0xE7, MRMDestMem, (outs), (ins