1 2013-06-10 00:00:57 <warren> TheUni: boost worked, trying oter
 2 2013-06-10 00:01:13 <TheUni> great, thanks
 3 2013-06-10 00:01:32 <TheUni> warren: is it possible for you to link me to the zips when done?
 4 2013-06-10 00:01:36 <warren> yes
 5 2013-06-10 00:15:46 <TheUni> warren: appeared to be successful?
 6 2013-06-10 00:19:23 <TheUni> welp, it's enough for a successful bitcoin build, so that's good enough to move on
 7 2013-06-10 00:35:33 <TheUni> warren: branch updated to build win32 if you feel like giving it a shot. this gitian branch needs to build against my autotools branch: https://github.com/theuni/bitcoin/tree/autotools-rfc-1
 8 2013-06-10 00:36:20 <warren> I'm out of time.  I'll try tomorrow if nobody else did.
 9 2013-06-10 00:37:06 <TheUni> no worries. thanks.
10 2013-06-10 00:44:37 <ethanbuchman> suppose i were foolish enough to try to understand the bit coin source code.  where do i even begin?!
11 2013-06-10 00:45:09 <Luke-Jr> Earth
12 2013-06-10 00:45:43 <work2heat> thats helpful
13 2013-06-10 00:46:25 <work2heat> seriously tho.  I'm a young/new programmer.  I mostly write in python.  but id love to be able to work through all the open source code out there. i just never know where to start...
14 2013-06-10 00:48:21 <TheUni> work2heat: come up with a problem, large or small. work til you fix it
15 2013-06-10 00:49:23 <TheUni> sometimes that means doodling a new icon and figuring out where to stick it. sometimes it means understanding the entire codebase to come up with the correct one-line fix
16 2013-06-10 00:50:02 <work2heat> but i don't even know where things are.  i scroll through the bitcoin github time to time thinking "now I'll understand something!", but alas, I have yet to.  is there documentation somewhere or what?  how are others expected to start working it?
17 2013-06-10 00:50:23 <TheUni> git grep
18 2013-06-10 00:51:20 <work2heat> touche!
19 2013-06-10 00:51:29 <Luke-Jr> work2heat: the RPC code is pretty nicely modularized now
20 2013-06-10 00:51:32 <Luke-Jr> rpc*.cpp
21 2013-06-10 00:51:41 <work2heat> whats that
22 2013-06-10 00:51:59 <TheUni> work2heat: to be clear, i'm an outsider as well. but i've been involved in several big projects, and that's how i start
23 2013-06-10 00:52:21 <work2heat> "remote procedure call"?
24 2013-06-10 00:52:27 <Luke-Jr> work2heat: seriously, I doubt you'll find anyone who knows it who is willing to hold your hand. LOOK. IT'S RIGHT IN FRONT OF YOU.
25 2013-06-10 00:52:45 <work2heat> just by greppin for whatever u feel like working on huh
26 2013-06-10 00:52:58 <work2heat> not looking for hand holding.  just pointers, tips,
27 2013-06-10 00:53:14 <Luke-Jr> I gave you a pointer.
28 2013-06-10 00:54:24 <work2heat> perhaps all that python has made me ignorant to pointers ;)
29 2013-06-10 00:54:27 <work2heat> :P
30 2013-06-10 01:34:43 <owowo> why is my bitcoind showing me "offline, has not been successfully broadcast yet" ?
31 2013-06-10 01:34:49 <owowo> *bitcoin-qt
32 2013-06-10 01:38:43 <Diablo-D3> because you're not connected to other peers?
33 2013-06-10 01:39:31 <owowo> 8 active connections...
34 2013-06-10 01:43:16 <Diablo-D3> owowo: were you connected and up to date when you sent that tx?
35 2013-06-10 01:44:52 <owowo> connected yes, but not up to date, but not being up to date never was a problem, The tx just showed 0 conf until it was up to date, but it was at least broadcast
36 2013-06-10 01:45:35 <owowo> it's not even showing ob blockexplorer
37 2013-06-10 01:56:49 <owowo> nvm it got broadcast
38 2013-06-10 02:05:35 <gribble> 240693
39 2013-06-10 02:05:35 <phantomcircuit> ;;bc,blocks
40 2013-06-10 02:13:54 <Vinnie_win> PHEW price coming back
41 2013-06-10 02:13:58 <Vinnie_win> fucking spam emails
42 2013-06-10 02:15:49 <owowo> exactly, mate ;o)
43 2013-06-10 03:46:17 <shesek> when preparing a transaction for hashing/signing, what script should I use for p2sh inputs? the original hashed output script (HASH_160 ... OP_EQUAL) or the original pre-hashed script?
44 2013-06-10 03:46:55 <shesek> (I'm referring to bitcoinj[s]'s hashTransactionForSignature connectedScript argument)
45 2013-06-10 04:31:40 <sipa> TheUni: which branch?
46 2013-06-10 04:34:05 <TheUni> sipa: gitian-cleanup. 1 sec though, just spotted a prob
47 2013-06-10 04:36:53 <sipa> TheUni: that does not include the autotools changes?
48 2013-06-10 04:37:21 <TheUni> sipa: no. i thought you could have gitian use discriptors for another branch?
49 2013-06-10 04:37:24 <TheUni> need me to merge em?