Matches for patch, 1691 total results Sorted by newest | relevance
Sun Aug 09 05:16:41 UTC 2015 <mod6> trinque: sig verifies & patch applies cleanly. thx again.
Sun Aug 09 03:52:01 UTC 2015 <mod6> yah, I left him a note to re-send a patch with a detached sig to the ML. can help or do it for him if required, etc.
Sun Aug 09 03:50:18 UTC 2015 <asciilifeform> didja have to use trinque's patch ?
Sun Aug 09 03:49:07 UTC 2015 <mod6> once we have that, and a new patch from trinque, i can complete my script and have a rotor that builds these test bundles with x86-64
Sat Aug 08 23:12:10 UTC 2015 <mod6> <+hanbot> re ml: where are sha256sums for, eg, http://therealbitcoin.org/ml/btc-dev/2015-February/000040.html (patch)? << Hi, in the case of that patch email, the SHA1 sum is embedded in the file name. For example: asciilifeform_dnsseed_snipsnip_192f7bc7c14c1d31c7b417c9cd77be51c4d255f2.patch -- if you were to download this patch, you could then run `sha1sum asciilifeform_dnsseed_snipsnip_192f7bc7c14c1d31c7b417c9cd77be51c4d255f2.patch` and it sh
Sat Aug 08 22:10:03 UTC 2015 <hanbot> re ml: where are sha256sums for, eg, http://therealbitcoin.org/ml/btc-dev/2015-February/000040.html (patch)?
Sat Aug 08 19:42:48 UTC 2015 <mod6> trinque: would you be opposed to resubmitting your patch for the rotor to the ML as a attachment with a detached sig? I have a list of concise steps that is basically a simple script to do all of the steps to build rotor/static-deterministic-stator just need to get that piece into place. that's the only manual step at this point.
Fri Aug 07 18:16:52 UTC 2015 <ascii_field> the 'patch' on my systems eats these happily, disregarding the extra bit
Fri Aug 07 04:23:22 UTC 2015 <phf_mobile> i have a mac os x patch, but as i recall that's the only change required, and since i don't understand the implications, i didn't post it. it works when building with clang, but needs investigation why duplicate function to begin with
Fri Aug 07 03:15:46 UTC 2015 <BingoBoingo> n6: Practice on different *nic first. Install OpenBSD upgrade to stable. May have to patch bitcoind, but learn building from source in very documented way.
Thu Aug 06 21:27:40 UTC 2015 <davout> ascii_field: if you could have a separate pgptron for checking sigs, and the ability to manually insert a signed patch into it?
Thu Aug 06 02:14:34 UTC 2015 <trinque> I actually grow to like the wiki suggestion best for the patch tree
Thu Aug 06 02:12:52 UTC 2015 <trinque> you've got "who signed this patch" and also "what is the parent node patch of this patch"
Thu Aug 06 02:12:31 UTC 2015 <assbot> Logged on 06-08-2015 01:59:06; *: BingoBoingo thinks whole problem is that 'patch' demands line numbers instead of using nearby lines of code as landmarks
Thu Aug 06 02:07:29 UTC 2015 <punkman> not that I'd mind patch deeds, but can basically deed patch hashes already
Thu Aug 06 01:59:21 UTC 2015 <mod6> that way it sort of also solves the problem of keeping track of who signed which patch. since deedbot stores these sigs in a horizontal fashion next to the address.
Thu Aug 06 01:59:06 UTC 2015 <*> BingoBoingo thinks whole problem is that 'patch' demands line numbers instead of using nearby lines of code as landmarks
Thu Aug 06 01:58:17 UTC 2015 <mod6> oh, i think he was saying that he would need to implement accepting a second argument and making it so that the URL contains a hash of the original plaintext patch.
Thu Aug 06 01:55:55 UTC 2015 <mod6> but what if we then, say, at the end of a testing/release cycle were to (instead of signing or as well as posting to the mailing list) post the plaintext patch and a detach signature from the originating author, myself & ben to deedbot as a perm storage for these patches?
Wed Aug 05 23:53:45 UTC 2015 <asciilifeform> but this is not enough, will need the hard-fuckyou-never-disconnect-from-nobles patch