00:00:00 --- log: started forth/17.08.07 00:59:11 --- quit: dys (Ping timeout: 240 seconds) 01:07:38 --- join: dys (~dys@2003:5b:203b:100:6af7:28ff:fe06:801) joined #forth 02:52:10 --- join: GeDaMo (~GeDaMo@212.225.125.110) joined #forth 02:55:29 --- quit: nighty- (Quit: Disappears in a puff of smoke) 03:12:19 --- quit: karswell_ (Read error: Connection reset by peer) 03:13:08 --- join: karswell_ (~user@207.91.199.146.dyn.plus.net) joined #forth 03:55:26 --- quit: rtmanpages (Ping timeout: 240 seconds) 04:48:23 --- quit: karswell_ (Read error: Connection reset by peer) 04:49:13 --- join: karswell_ (~user@207.91.199.146.dyn.plus.net) joined #forth 05:05:57 --- quit: leaverite (Quit: leaverite) 05:05:58 --- quit: wa5qjh (Remote host closed the connection) 05:32:07 --- quit: karswell_ (Ping timeout: 255 seconds) 06:25:41 --- part: mtsd left #forth 11:39:11 --- quit: dys (Ping timeout: 240 seconds) 11:51:57 This channel isn't too lively, is it? 11:52:29 --- join: dys (~dys@tmo-107-27.customers.d1-online.com) joined #forth 11:53:47 Says the zombie :P 11:54:10 Hey, at least I don't have to worry about my BAC after the party 12:04:07 how is it that I am routinely shocked at how bad software engineers are at record-keeping 12:04:48 right now I'm trying to figure out what version of an open source package we have in our repo, and there are years of updates to it with the comment "updated the package" 12:04:52 or "pulled from git" 12:05:01 no indication of which commit was taken whatsoever 12:05:33 That might be a sign that the maintainer didn't give it more thought than what they posted 12:05:35 honestly, why the hell does the guy writing that think there is a comment field on code submissions? 12:05:55 does he actually think that "updated the package" is useful information? 12:06:02 could be 12:06:10 They may not be aware something more is needed 12:06:40 tbh, I usually struggle some myself, but then I'm a complete newbie and am still very much learning 12:06:46 I also love the "merged from x branch" comments 12:06:56 we use perforce here and it doesn't tell you where a merge came from 12:07:03 or what change it was 12:07:21 so "merged from x branch" is not useful. "merged from x branch change number y" is 12:07:23 Doesn't Git do that? 12:07:33 yeah 12:07:47 perforce is dumb in a lot of ways, and I complain about it a lot too 12:07:47 That might be the issue. They might just be used to Git 12:08:01 doubt it 12:08:18 most of the people I see doing stuff like that have never touched git in their life 12:08:33 or I'd be surprised if they had, anyway 12:08:53 Sounds like someone needs to post something with commit guidelines 12:08:59 if such doesn't already exist 12:09:15 heh 12:09:39 yeah, fat chance of that 12:11:32 I agree, though - it is probably an indication that they didn't realize more information would be helpful... which is a sad indication that they've probably never actually used their scm beyond as a method to publish their changes 12:13:39 --- join: Zarutian_PI2 (~3.1415@89.17.133.173) joined #forth 12:13:39 --- quit: Zarutian_PI (Read error: Connection reset by peer) 12:13:50 --- nick: Zarutian_PI2 -> Zarutian_PI 13:09:03 --- quit: GeDaMo (Remote host closed the connection) 14:04:39 --- join: rtmanpages (~rtmanpage@244.sub-174-204-0.myvzw.com) joined #forth 15:09:26 --- quit: dys (Ping timeout: 255 seconds) 16:11:50 --- join: wa5qjh (~quassel@175.158.225.209) joined #forth 16:12:08 --- join: leaverite (~Thunderbi@175.158.225.209) joined #forth 17:51:19 --- quit: johnmark (Quit: Leaving) 17:54:42 --- join: nighty- (~nighty@kyotolabs.asahinet.com) joined #forth 20:12:47 --- join: karswell_ (~user@207.91.199.146.dyn.plus.net) joined #forth 20:17:29 --- quit: groovy2shoes (Ping timeout: 240 seconds) 20:37:58 --- quit: Bunny351 (Ping timeout: 255 seconds) 21:33:47 --- join: Bunny351 (~Bunny351@p4FD2DE75.dip0.t-ipconnect.de) joined #forth 21:53:19 --- join: dys (~dys@tmo-123-192.customers.d1-online.com) joined #forth 21:56:43 --- join: proteusguy (~proteus-g@49.228.109.113) joined #forth 21:56:43 --- mode: ChanServ set +v proteusguy 22:07:46 --- join: mtsd (3e5f4c02@gateway/web/freenode/ip.62.95.76.2) joined #forth 23:47:20 --- quit: dys (Ping timeout: 268 seconds) 23:59:59 --- log: ended forth/17.08.07