Matches for patch, 1691 total results Sorted by newest | relevance
Thu Mar 12 04:58:48 UTC 2015 <mod6> decimation: i think, in interest of time.. perhaps (with your help/testing) we'll post a patch for the makefile & the auto.sh post release.
Thu Mar 12 04:53:25 UTC 2015 <mod6> so i'll re-submit that makefile patch and what will be v0.0.5 of the mod'd pogo script (with 'no-dso')
Thu Mar 12 04:40:26 UTC 2015 <asciilifeform> it doesn't, if the https-snipper patch was merged.
Thu Mar 12 03:07:19 UTC 2015 <mod6> asciilifeform: because how we'll roll out the release: 1) I'll patch the source myself and put it in a 'bitcoin' directory 2) i'll place the 'auto.sh' in the same parent directory as 'bitcoin' directory 3) tar those up 4) end user will unpack archive and execute `auto.sh'
Thu Mar 12 02:44:32 UTC 2015 <mod6> everyone will start with an already patched codebase, unless they want to patch it manually or wrestle with one of the 2 scripts we have for this purpose
Thu Mar 12 02:43:40 UTC 2015 <mod6> i'll use it to patch the source code, then i'll bundle up the release.
Thu Mar 12 02:33:19 UTC 2015 <mod6> oh we're all discussing them pulling down the patch files, verifing the patch sigs and patching the base code
Thu Mar 12 02:29:25 UTC 2015 <decimation> Verifing patch signatures..
Wed Mar 11 00:29:28 UTC 2015 <asciilifeform> on account of being a software patch away from full auto
Tue Mar 10 21:59:39 UTC 2015 <ascii_field> but did you really expect microshit to patch without opening a new orifice? because that'd be a first.
Tue Mar 10 21:57:36 UTC 2015 <scoopbot> New post on Qntra.net by Bingo Boingo: http://qntra.net/2015/03/windows-stuxnet-patch-left-vulnerability-open/
Sun Mar 08 18:38:19 UTC 2015 <asciilifeform> ben_vulpes: short summary: patch submitted by google chrome devs themselves; supposedly to simplify their sandbox 'jail' mechanism
Sun Mar 08 18:33:39 UTC 2015 <assbot> Linux-Kernel Archive: [PATCH v6 7/9] seccomp: implement SECCOMP_FILTER_FLAG_TSYNC ... ( http://bit.ly/18sRul2 )
Wed Mar 04 18:29:17 UTC 2015 <nubbins`> each patch is intended to be small enough that a human can read and understand it
Wed Mar 04 14:29:07 UTC 2015 <mod6> jurov: so as far as shorter release cycles, i think going forward they will be. the foundation will focus on say, one specific problem and then tackle it, patch it, and then regression test, release.
Wed Mar 04 14:02:53 UTC 2015 <mod6> to make it build statically, there is another patch that I still need to submit yet (probably today) and another patch & full source to submit of a modified poratronic build script.
Wed Mar 04 14:00:46 UTC 2015 <jurov> because it does include the version bump patch
Tue Mar 03 21:30:20 UTC 2015 <thestringpuller> but that relates to the OpenBSD patch
Mon Feb 23 22:44:41 UTC 2015 <plonky> with all the patch included to kernel compilation in archlinux
Mon Feb 23 02:55:35 UTC 2015 <mod6> last note: this is all predicated on the fact that one would have run the v0.0.8 perl script to patch the R.I. So you might need to alter line 62 to point to the correct bitcoin build directory.