[00:54:20] *** Joins: tomzawadzki (tomzawadzk@nat/intel/x-txirqkumspnjurra) [01:58:18] *** Joins: tkulasek (~tkulasek@192.55.54.39) [02:02:49] *** Quits: Shuhei (caf6fc61@gateway/web/freenode/ip.202.246.252.97) (Ping timeout: 260 seconds) [06:11:48] *** Quits: tkulasek (~tkulasek@192.55.54.39) (Remote host closed the connection) [07:36:15] *** Parts: lhodev (~Adium@66-90-218-190.dyn.grandenetworks.net) () [07:36:20] *** Joins: lhodev (~Adium@66-90-218-190.dyn.grandenetworks.net) [08:00:52] *** Quits: sethhowe (~sethhowe@134.134.139.83) (Remote host closed the connection) [08:02:29] *** Joins: sethhowe (~sethhowe@134.134.139.83) [08:20:53] reminder: Asia friendly community meeting is in about 12.5 hrs from now... [08:21:33] drv: jimharris: Could one of you take a look at https://review.gerrithub.io/#/c/403745/ and assuming you're ok with it, proceed with the merge? I've got a series of forthcoming changes all of which will modify the same file (but intentionally broken into separate patches). I think that if I edit the current state of the file (with the aforementioned change) and submit it for your review, then won't the diff in gerrit highlight both th [08:21:34] at change and the new? Alternatively, if I checked out from master and instantiated a new branch, then the change to that would be isolated, but would likely like to a merge conflict, right? [08:22:24] s/likely like/likely lead/ [08:47:31] Hmmm… Just re-read http://www.spdk.io/development/#multi. That seems to suggest the patch submission method I should pursue, esp. in light that I'll be touching the same file for several more, separate patches. I just hope the rebase's will operate cleanly or at least minimize any merges. [09:03:22] *** Quits: tomzawadzki (tomzawadzk@nat/intel/x-txirqkumspnjurra) (Ping timeout: 264 seconds) [09:05:22] lhodev: I'll take a look in a moment [09:05:42] Thx Daniel. [09:05:45] and yes, you can definitely use the patch series functionality for the iSCSI change, since they're all closely related [09:05:54] and that will avoid a lot of needless rebasing :) [09:05:58] Will do [09:16:45] lhodev: one small note for future patches - we try to prefix the commit message with the relevant library or subsystem, so these patches would probably be "iscsi: ..." rather than lib [09:17:11] but we're not particularly consistent either, so I don't think anyone will get too worked up about it :) [09:18:53] drv: Oh, ok. I'd seen instances of "lib" prefixes in the git log before I began hence that selection, but I'll be happy to switch to "iscsi:". However, having that said, given that I've started a *series*, would you prefer I remain consistent with my "lib:" prefix til the end of these? [09:19:43] I'd say probably use iscsi for the later ones, but it's not super important [09:19:56] just makes it easier to skim through e.g. 'git log --pretty=oneline' [09:20:46] Sure [09:37:04] *** Joins: param (7ab2ceb1@gateway/web/freenode/ip.122.178.206.177) [09:38:06] which is free version of irc channel that i can use... and in few clients I am not able to see the chat history.. [09:38:20] *irc client not channel [09:39:05] param: There are a variety of options I supposed depending on the OS on which you wish to run it. [09:39:32] param: I'm using irssi + screen - this way you will always be connected, so you will have all the history [09:40:01] lhodev : i will be using mac and windows.. [09:40:21] but for that you will need someunix server [09:40:40] mszwed : sure.. ill take a look.. [09:41:07] param: you may also inspect https://ci.spdk.io/irclog/ [09:42:16] param: On a Mac, I'm using Adium, but I'm not very happy with it. I intend to research other options. [09:44:03] lhodev : thanks for the log link.. that would be really helpfull.. [09:44:42] jim : drv : which card can i start working on.. [09:44:50] any suggestions.. [09:45:26] hi param, did you see Jim's message about adding the remove listener function to rpc.py? [09:45:48] I missed that in my review, but we should make sure it is callable from our rpc wrapper [09:46:13] drv : oh.. okay...then ill add that function.. [09:46:28] thanks, should be pretty straightforward (just copy the pattern of the existing RPC methods) [09:46:33] and then we can figure out what makes sense to work on next [09:46:49] yeah. sure.. [10:09:55] *** Quits: param (7ab2ceb1@gateway/web/freenode/ip.122.178.206.177) (Ping timeout: 260 seconds) [12:16:42] *** Quits: lhodev (~Adium@66-90-218-190.dyn.grandenetworks.net) (Ping timeout: 256 seconds) [14:34:30] *** Joins: lhodev (~Adium@inet-hqmc06-o.oracle.com) [15:57:52] *** Joins: Shuhei (caf6fc61@gateway/web/freenode/ip.202.246.252.97) [17:51:49] *** Quits: lhodev (~Adium@inet-hqmc06-o.oracle.com) (Remote host closed the connection) [17:52:08] *** Joins: lhodev (~Adium@66-90-218-190.dyn.grandenetworks.net) [19:20:21] *** Parts: lhodev (~Adium@66-90-218-190.dyn.grandenetworks.net) () [19:20:24] *** Joins: lhodev (~Adium@66-90-218-190.dyn.grandenetworks.net) [20:03:54] *** Joins: johnmeneghini (~johnmeneg@pool-100-0-53-181.bstnma.fios.verizon.net) [20:04:07] Hellow [20:04:24] Are we having the SPDK Community meeting now? [20:04:48] johnmeneghini: I tried to connect, but was unable to. [20:05:02] I tried too. [20:05:52] And there are three (3) cards on tonight's agenda according to Trello. Oh wait….Did it get moved to tomorrow instead? [20:06:05] https://trello.com/b/DvM7XayJ/spdk-community-meeting-agenda [20:07:01] It's confusing because the date shown is "Thu Mar 16th". But Thu is Mar 15th. [20:07:44] Alas, I also recall earlier someone sending out a msg here on the IRC that the meeting was some X hours away, so it should be now. [20:09:06] I think that was supposed to be Thursday March 15 04:00 UTC == Wednesday March 14 11:00 pm EST [20:09:16] Right [20:09:31] Maybe the problem is that we move from EST to EDT in the US? [20:12:39] Yup, that's it. So, I guess it doesn't start for another hour; well, 48 minutes. [20:12:40] looking at www.wordtimebuddy.com, it's Thurs Mar 15, 03:00 UTC [20:12:58] So I think we are an hour early [20:13:24] Suddenly sorry I didn't make a Starbucks run earlier…. [20:13:32] LOL [20:18:45] *** Quits: johnmeneghini (~johnmeneg@pool-100-0-53-181.bstnma.fios.verizon.net) (Quit: Leaving.) [20:19:24] *** Joins: johnmeneghini (~johnmeneg@pool-100-0-53-181.bstnma.fios.verizon.net) [20:23:34] *** Quits: Shuhei (caf6fc61@gateway/web/freenode/ip.202.246.252.97) (Ping timeout: 260 seconds) [20:24:14] *** Quits: johnmeneghini (~johnmeneg@pool-100-0-53-181.bstnma.fios.verizon.net) (Client Quit) [20:24:38] *** Joins: johnmeneghini (~johnmeneg@pool-100-0-53-181.bstnma.fios.verizon.net) [20:39:41] *** Quits: johnmeneghini (~johnmeneg@pool-100-0-53-181.bstnma.fios.verizon.net) (Quit: Leaving.) [20:40:03] *** Joins: johnmeneghini (~johnmeneg@pool-100-0-53-181.bstnma.fios.verizon.net) [20:46:01] heh, yeah its in 15 minutes... why can't the world be on one time zone right?? [20:48:55] I just turned on advanced time zone support in my calendar app and edited the times. Hopefully, that'll do it. [20:54:13] *** Quits: johnmeneghini (~johnmeneg@pool-100-0-53-181.bstnma.fios.verizon.net) (Quit: Leaving.) [20:55:17] *** Joins: johnmeneghini (~johnmeneg@pool-100-0-53-181.bstnma.fios.verizon.net) [21:01:30] *** Joins: Shuhei (caf6fc61@gateway/web/freenode/ip.202.246.252.97) [21:10:03] *** Quits: johnmeneghini (~johnmeneg@pool-100-0-53-181.bstnma.fios.verizon.net) (Quit: Leaving.) [21:10:25] *** Joins: johnmeneghini (~johnmeneg@pool-100-0-53-181.bstnma.fios.verizon.net) [21:20:08] *** Quits: johnmeneghini (~johnmeneg@pool-100-0-53-181.bstnma.fios.verizon.net) (Quit: Leaving.)