--- Day changed Tue Jun 02 2020 00:53 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 260 seconds] 01:18 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #bitcoin-core-pr-reviews 02:41 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 260 seconds] 03:05 -!- Caterina41Ruecke [~Caterina4@static.57.1.216.95.clients.your-server.de] has joined #bitcoin-core-pr-reviews 03:10 -!- Caterina41Ruecke [~Caterina4@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 260 seconds] 03:30 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-pr-reviews 04:32 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 04:36 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #bitcoin-core-pr-reviews 05:00 -!- likewhoa [~likewhoa@li1078-231.members.linode.com] has quit [Ping timeout: 258 seconds] 05:01 -!- likewhoa [~likewhoa@li1078-231.members.linode.com] has joined #bitcoin-core-pr-reviews 05:02 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 258 seconds] 05:56 -!- Zenton [~user@unaffiliated/vicenteh] has joined #bitcoin-core-pr-reviews 07:03 -!- icota[m] [icotamatri@gateway/shell/matrix.org/x-wfhuaxymifzteebb] has quit [Quit: Idle for 30+ days] 07:12 -!- dfmb_ [~dfmb_@unaffiliated/dfmb/x-4009105] has joined #bitcoin-core-pr-reviews 07:12 -!- dfmbbtc [~dfmb_@unaffiliated/dfmb/x-4009105] has joined #bitcoin-core-pr-reviews 07:13 -!- dfmbbtc [~dfmb_@unaffiliated/dfmb/x-4009105] has quit [Remote host closed the connection] 07:20 -!- dfmb_ [~dfmb_@unaffiliated/dfmb/x-4009105] has quit [Quit: Leaving] 07:28 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 256 seconds] 07:45 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-core-pr-reviews 08:06 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 260 seconds] 08:29 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Read error: Connection reset by peer] 08:29 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 08:29 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection] 08:29 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Remote host closed the connection] 08:29 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Read error: Connection reset by peer] 08:32 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #bitcoin-core-pr-reviews 08:32 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-pr-reviews 08:35 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #bitcoin-core-pr-reviews 08:35 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Client Quit] 08:36 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #bitcoin-core-pr-reviews 08:39 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-pr-reviews 08:40 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-core-pr-reviews 08:41 -!- troygiorshev [~troygiors@CPEdcef09a0ed55-CM0c473d74be00.cpe.net.cable.rogers.com] has joined #bitcoin-core-pr-reviews 08:56 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 09:09 -!- slivera [~slivera@103.231.88.10] has quit [Remote host closed the connection] 09:20 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-pr-reviews 09:23 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 09:23 -!- vasild_ is now known as vasild 09:54 -!- dfmb_ [~dfmb_@unaffiliated/dfmb/x-4009105] has joined #bitcoin-core-pr-reviews 10:03 -!- setpill [~setpill@unaffiliated/setpill] has quit [Quit: o/] 10:04 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 10:04 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-pr-reviews 10:09 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-core-pr-reviews 10:11 -!- dr-orlovsky [~Dr_Orlovs@31.14.40.19] has joined #bitcoin-core-pr-reviews 10:12 -!- troygiorshev [~troygiors@CPEdcef09a0ed55-CM0c473d74be00.cpe.net.cable.rogers.com] has quit [Ping timeout: 256 seconds] 10:15 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #bitcoin-core-pr-reviews 11:00 < jonatack> Someone asked me a question that I'm posting a shorter version of here, so more people can respond or benefit: "How do you keep track of whats happening? Its overwhelming with all the open issues and PRs. Are there any tools to make it manageable?" 11:06 < jnewbery> I don't try to keep track of everything. I have the open PRs that I'm reviewing/working on, and that keeps me busy 11:08 < jonatack> Same. I try to look at the high-priority PRs, some of the other PRs that interest me, and sometimes devs ping over irc to discuss/ask for review. I mostly use GitHub email notifications and IRC. Starting to use github-cli, too. Also, https://bitcoinacks.com is back online. 11:09 < pinheadmz> woha that site is crazy 11:10 < jonatack> If time permits, I woulln't mind fixing some of the ACK parsing in it. Bitcoin-ACKs is now in the bitcoin-core repo. 11:47 -!- troygiorshev [~troygiors@CPEdcef09a0ed55-CM0c473d74be00.cpe.net.cable.rogers.com] has joined #bitcoin-core-pr-reviews 11:57 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!] 12:16 -!- troygiorshev [~troygiors@CPEdcef09a0ed55-CM0c473d74be00.cpe.net.cable.rogers.com] has quit [Ping timeout: 260 seconds] 12:16 -!- dfmb_ [~dfmb_@unaffiliated/dfmb/x-4009105] has quit [Quit: Leaving] 12:21 -!- troygiorshev [~troygiors@CPEdcef09a0ed55-CM0c473d74be00.cpe.net.cable.rogers.com] has joined #bitcoin-core-pr-reviews 12:34 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 12:34 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-pr-reviews 12:42 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-pr-reviews 13:48 < raj_149> Oh the bitcoinack.com is really neat. I will start looking up on github-cli too. Weird thing about github is it wont show my latest activities but only the old ones in my feed top. Is that same for everybody? I am in constant pursuit to get my workflow smoother, does github desktop helps? 13:52 < jonatack> raj_149: subjective opinion: i think github desktop is a good way to forget how to use git on the command line... avoid ;) ... in general, afaik there's no magic bullet or shortcut 13:56 < jonatack> and github-cli is improving, at v0.9 it's good for filtering issues and PRs by labels and attempting to be useful for simple review, but not quite ready yet for real review on the command line. i am waiting for the upcoming version 1.0 14:04 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Ping timeout: 240 seconds] 14:06 -!- Robin53Bosco [~Robin53Bo@static.57.1.216.95.clients.your-server.de] has joined #bitcoin-core-pr-reviews 14:11 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-core-pr-reviews 14:12 -!- Robin53Bosco [~Robin53Bo@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 260 seconds] 14:30 -!- mol_ [~mol@unaffiliated/molly] has joined #bitcoin-core-pr-reviews 14:33 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 256 seconds] 14:49 -!- slivera [~slivera@103.231.88.28] has joined #bitcoin-core-pr-reviews 16:00 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 16:01 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-pr-reviews 16:09 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 240 seconds] 16:23 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #bitcoin-core-pr-reviews 16:44 -!- troygiorshev [~troygiors@CPEdcef09a0ed55-CM0c473d74be00.cpe.net.cable.rogers.com] has quit [Ping timeout: 264 seconds] 17:03 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 17:04 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-pr-reviews 21:20 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #bitcoin-core-pr-reviews 21:23 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 21:23 -!- vasild_ is now known as vasild 22:50 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 260 seconds] 23:38 < raj_149> jonatack: thanks. That was a very helpful response. 23:38 < raj_149> Can someone point me to where the netgroup for a node is being calculated? What exactly is a netgroup?