Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2017-05-12

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:35 gem joined #gluster-dev
00:37 shaunm joined #gluster-dev
01:21 ankitr joined #gluster-dev
01:21 gyadav__ joined #gluster-dev
01:48 ilbot3 joined #gluster-dev
01:48 Topic for #gluster-dev is now Gluster Development Channel - http://gluster.org | For general chat go to #gluster | Patches - http://review.gluster.org/ | Channel Logs - https://botbot.me/freenode/gluster-dev/ & http://irclog.perlgeek.de/gluster-dev/
02:02 pranithk1 joined #gluster-dev
02:18 PotatoGim Does anyone can reviwe it? https://review.gluster.org/#/c/17246/2
02:55 gem_ joined #gluster-dev
03:39 nbalacha joined #gluster-dev
03:42 itisravi joined #gluster-dev
03:47 sthakkar joined #gluster-dev
03:51 atinmu joined #gluster-dev
03:52 atinmu itisravi, https://fstat.gluster.org/weeks/1
03:53 riyas joined #gluster-dev
04:12 gem joined #gluster-dev
04:12 jiffin joined #gluster-dev
04:15 gem joined #gluster-dev
04:31 ankitr joined #gluster-dev
04:36 ppai joined #gluster-dev
04:37 ankitr joined #gluster-dev
04:56 skumar joined #gluster-dev
05:03 amarts joined #gluster-dev
05:04 karthik_us joined #gluster-dev
05:09 aravindavk joined #gluster-dev
05:22 pkalever joined #gluster-dev
05:23 poornima joined #gluster-dev
05:23 sanoj joined #gluster-dev
05:24 jiffin joined #gluster-dev
05:25 ndarshan joined #gluster-dev
05:27 Shu6h3ndu joined #gluster-dev
05:43 msvbhat joined #gluster-dev
05:48 itisravi joined #gluster-dev
05:54 kotreshhr joined #gluster-dev
05:55 kotreshhr left #gluster-dev
05:59 kdhananjay joined #gluster-dev
06:19 gyadav joined #gluster-dev
06:28 karthik_us joined #gluster-dev
06:47 kdhananjay joined #gluster-dev
07:08 karthik_us joined #gluster-dev
07:13 ankitr joined #gluster-dev
07:13 ppai joined #gluster-dev
07:17 msvbhat joined #gluster-dev
07:37 rafi1 joined #gluster-dev
07:46 ankitr joined #gluster-dev
07:55 ankitr joined #gluster-dev
07:57 msvbhat joined #gluster-dev
08:11 ankitr joined #gluster-dev
08:39 atinmu joined #gluster-dev
08:43 sthakkar joined #gluster-dev
08:54 ankitr joined #gluster-dev
08:58 msvbhat joined #gluster-dev
09:03 msvbhat_ joined #gluster-dev
09:07 ankitr joined #gluster-dev
09:19 percevalbot joined #gluster-dev
09:37 rafi joined #gluster-dev
09:44 nbalacha joined #gluster-dev
09:46 atinmu joined #gluster-dev
09:51 sthakkar joined #gluster-dev
10:00 ppai joined #gluster-dev
10:06 sthakkar joined #gluster-dev
10:08 itisravi karthik_us: do you mind replying to atinmu's mail for fav-child-policy.t?
10:09 karthik_us itisravi, replying
10:09 itisravi karthik_us: cool
10:12 ankitr joined #gluster-dev
10:41 aravindavk joined #gluster-dev
10:43 sthakkar joined #gluster-dev
10:44 ankitr joined #gluster-dev
10:46 gem_ joined #gluster-dev
10:54 atinmu joined #gluster-dev
11:04 ndevos jiffin: are you ok with my reply in https://review.gluster.org/17189 ?
11:23 jiffin ndevos: I have given +1, does that sound okay?
11:23 ndevos jiffin: yes, thats fine, thanks!
11:55 nbalacha can someone please merge https://review.gluster.org/#/c/16163/?
12:04 kkeithley nbalacha: done
12:04 nbalacha kkeithley, thank you
12:04 nbalacha kkeithley++
12:04 glusterbot nbalacha: kkeithley's karma is now 188
12:07 ndevos backport bomb! 5 patches for 3 releases - https://review.gluster.org/#/q/project:glusterfs+status:open+message:nfs/nlm
12:11 ppai joined #gluster-dev
12:15 uebera|| joined #gluster-dev
12:41 vbellur joined #gluster-dev
12:42 skumar joined #gluster-dev
12:48 gyadav joined #gluster-dev
13:16 jiffin1 joined #gluster-dev
13:25 shyam joined #gluster-dev
13:38 gyadav joined #gluster-dev
13:58 aravindavk joined #gluster-dev
14:10 jiffin joined #gluster-dev
14:28 riyas joined #gluster-dev
14:28 lpabon joined #gluster-dev
14:33 gyadav joined #gluster-dev
14:38 PotatoGim can someone please review it? https://review.gluster.org/#/c/17246/
15:00 gem_ joined #gluster-dev
15:04 wushudoin joined #gluster-dev
15:04 shyam PotatoGim: The bug in the commit is against "mainline", the practice for backports is to clone the mainline bug and use that to submit the code against released branches
15:05 shyam PotatoGim: Here are the workflows: https://gluster.readthedocs.io/en/latest/Developer-guide/Backport-Guidelines/ and https://gluster.readthedocs.io/en/latest/Developer-guide/Development-Workflow/
15:05 shyam If that can be corrected, we can merge this change, if it is a bit overwhelming, let us know and we can take care of it for you this time!
15:36 msvbhat joined #gluster-dev
15:36 msvbhat_ joined #gluster-dev
16:16 vbellur1 joined #gluster-dev
16:17 vbellur joined #gluster-dev
16:18 vbellur joined #gluster-dev
16:18 vbellur joined #gluster-dev
16:20 percevalbot joined #gluster-dev
16:23 vbellur joined #gluster-dev
16:42 ndevos shyam: care to review https://review.gluster.org/17177 ? jeff merged the test-case already, which will now fail in the master branch :-/
16:43 ndevos https://review.gluster.org/17216 is the test-case, fwiw
16:43 shyam ndevos: Looking at it now
16:43 ndevos shyam++ thanks!
16:43 glusterbot ndevos: shyam's karma is now 10
16:44 * ndevos steps out for the weekend
16:44 shyam We need better dependency management of commits in gerrit, or are we missing doing something? I did this a few days back as well (merged a dependent patch)
16:44 ndevos yeah, in earlier versions of Gerrit the dependency tracking was better, the (unmerged) parent patches were listed much clearer
16:46 shyam Yes, I remember that as well (a bit vaugely though)
16:46 shyam Reading this if it makes sense: https://www.mediawiki.org/wiki/Gerrit/Advanced_usage#Create_a_dependency
16:46 ndevos now its up the component maintainers and developers posting the patches, but every now and then someone else helps out with merging things and they may not be aware of the dependencies
16:47 msvbhat joined #gluster-dev
16:47 msvbhat_ joined #gluster-dev
16:48 ndevos well, the dependency in Gerrit is there, it is just that you can sometimes submit (makes Gerrit do a 'git cherry-pick') of patches, in case there are no conflicts
16:48 ndevos here, one patch implements the functionality, and a 2nd patch on top does the testing - no conflicts by adding the new test-case
16:53 ndevos I dont think we can easily prevent this for other cases either... what if a public function/macro/struct gets renamed and an other unrelated patch adds a new call/usage of that pre-renamed symbol
16:54 ndevos anyway, weekend!
16:54 shyam ndevos: Enjoy! :) we will check on this later...
16:54 ndevos shyam: thanks :)
16:55 ndevos shyam: just expect that any new/rebased changes will fail regression testing now... :-(
18:03 shyam joined #gluster-dev
18:37 vbellur joined #gluster-dev
19:50 rastar joined #gluster-dev
20:07 msvbhat joined #gluster-dev
20:10 msvbhat_ joined #gluster-dev
20:35 ingard_ joined #gluster-dev
20:38 shyam joined #gluster-dev
22:05 nh2 joined #gluster-dev

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary