quotable6

query

p6dev

result-#moarvm.md

Oh wait, are you confusing here with the p6dev -> perl6-dev transition? :)
jnthn: on #p6dev nine just realized that Inline::Perl5's issues may be reframe related
tomboy64: no, i think that would be #p6dev, ideally with a PR to http://github.com/perl6/nqp

result-#p6dev.md

soo, this is #p6dev freenode?
users on #p6dev but not #perl6-dev ( DrForr Hotkeys japhb perlpilot pmichaud_ raydiak saaki sno synopsebot6 teatime tomboy65 Ven )
likes #p6dev...
#perl6-dev is a lot clearer than #p6dev -- and it's not a big deal either way
Considering we have a number of #perl6-* and #p6dev is the only one that doesn't match it makes sense for a rename.
so #p6dev → #perl6-dev ?
leaves p6devand joins perl6-dev
'p6dev' is not a top level freenode accredited project, so we're currently (a) inconsistent with the naming of our other channels (b) violating freenode guidelines (c) making it impossible for me to fix this channel if it breaks
(if you're intentionally trying to hide then we need to move to ##p6dev btw)
moritz: note the difference between #perl6-dev and #p6dev
#p6dev being here, #perl6-dev being over there :)
well, we're kicking out #p6dev
morning, #p6dev
good *, #p6dev
good night, #p6dev!
we should have discussed thin in #perl6, since at least me isn't terribly serious about most of this, but #p6dev is the "everybody should backlog this only"
nqp: See http://irclog.perlgeek.de/p6dev/2016-05-09#i_12456101.
http://irclog.perlgeek.de/p6dev/2016-05-07#i_12446159
good night, #p6dev
jnthn: http://irclog.perlgeek.de/p6dev/2016-05-06#i_12442407 is where it starts
psch: I suspect, it was the merge of the precomp branch (cmp http://irclog.perlgeek.de/p6dev/2016-05-02#i_12422526 and http://irclog.perlgeek.de/perl6/2016-05-03#i_12429980 )
lizmat: I assume the failing 6.c tests are the same as http://irclog.perlgeek.de/p6dev/2016-05-04#i_12431564 - I'm opening a ticket, making it a blocker for the next release.
eh, #p6dev :-)
rakudo/nom: See http://irclog.perlgeek.de/p6dev/2016-05-02#i_12423404
'night, #p6dev
gnight, #p6dev
rakudo/nom: See http://irclog.perlgeek.de/p6dev/2016-04-26#i_12394560
jnthn: re http://irclog.perlgeek.de/p6dev/2016-04-23#i_12381803
...my camelia query used to be win5, now that's p6dev :S
wow, so much #p6dev chat today :)
rakudo/nom: As per http://irclog.perlgeek.de/p6dev/2016-04-22#i_12378252
good night, #p6dev!
morning, #p6dev
oh, #p6dev not #perl6
oh, this is #p6dev... :)
sure, a p6dev weekly (or maybe monthly, or maybe just interesting discussion summarized and structured) would be neat, but who's gonna write it..? :)
I was under the impression that we would have this type of discussion on #p6dev rather than #perl6
I would therefore suggest that *if* we have such a discussion on a place other than #p6dev, someone should at least put a link to the discussion on #p6dev
+1 +1 +1 on posting important discussions on #p6dev
good night, #p6dev!
good night, #p6dev!
enough for today, o/ #p6dev
so good night, #p6dev!
rakudo/nom: Travis reporting to #p6dev
nqp: Travis reporting to #p6dev
good night, #p6dev!
good night, #p6dev
good *, #p6dev
[Coke]: re http://irclog.perlgeek.de/p6dev/2016-03-17#i_12201282 , my experiences with branches being reviewed, are not favorable
b2gills: re http://irclog.perlgeek.de/p6dev/2016-03-17#i_12202826 , the PR doesn't cleanly apply anymore :-(
i feel quite a bit relieved that we have #p6dev now; i can get away with not backlogging all of #perl6 now
good *, #p6dev :-)
o/ #p6dev
o/ #p6dev
good night, #p6dev :-)

result-#perl6-dev.md

moritz_: hey, ilbot3 is now the only thing other than my in the old #p6dev - disconnect it and I'll turn off the lights on the channel on my way out? :)
http://irclog.perlgeek.de/p6dev/2016-04-23#i_12381309
moritz: I just noticed that dalek is still logged into #p6dev, that seems unneccessary ?
Why does travis report in #p6dev?
morning, #p6dev
by the way, travis-ci is screaming its lungs out on #p6dev
travis is reporting in p6dev, not perl6-dev
should dalek report commits here rathern then to #p6dev?
for all intents and purposes, #p6dev doesn't exist
just saw that dalek still reports roast and nqp commits to #p6dev
I figured that mirrored #p6dev as close as possible

result-#perl6.md

1 Jan 2018 02:28Z <timotimo> moritz: quotable6 can't grab irc data right now because https://irclog.perlgeek.de/p6dev/2017-12-31 gives a 500 internal server error if Accept: application/json is set :(
.tell timotimo I can't reproduce your error; $ curl -H 'Accept: application/json' https://irclog.perlgeek.de/p6dev/2017-12-31; echo $? gives me {"header":["id","nick","timestamp","line"],"channel":"p6dev","day":"2017-12-31","rows":[]} 0
16:20Z <moritz> timotimo: I can't reproduce your error; $ curl -H 'Accept: application/json' https://irclog.perlgeek.de/p6dev/2017-12-31; echo $? gives me {"header":["id","nick","timestamp","line"],"channel":"p6dev","day":"2017-12-31","rows":[]} 0
.tell moritz quotable6 can't grab irc data right now because https://irclog.perlgeek.de/p6dev/2017-12-31 gives a 500 internal server error if Accept: application/json is set :(
well, we had p6dev before that
Hotkeys: I noticed you are on #p6dev which was rename to #perl6-dev
now the only person that is in #p6dev, but not #perl6-dev is saaki
psch: ohh, I'm in #p6dev
also synopsebot6 (and both exiting #p6dev)
but at the same time camelia was on #p6dev but there is no such entry in this config
reporting modules, which have wide audience/interest, here, would mirror #perl. and then you can report core to #p6dev per current config.
we have #p6dev
teatime: another point to note is that actual development now happens on #p6dev
ZoffixW: hoelzro++ just signed up for the May release (over in #p6dev or #p6release or so); are you available for the May Star release or the June compiler release?
so funny that #p6dev is amok and #perl6 is dead right now xD
(i also thought i was in #p6dev :P)
Xliff: maybe someone in #p6dev or #moarvm might know :\
no, no #p6dev ;-)
mst: probably better asked on #moarvm or #p6dev
MadcapJake: check #p6dev for that discussion
tomboy64: this or #p6dev
TimToady: I don't mean to tug your attention too much, but did you have time to ponder http://irclog.perlgeek.de/p6dev/2016-04-22#i_12376718 ?
azawawi: fwiw much of the rakudo development discussion has moved to #p6dev
can I ask a general p6dev question; I'm trying to *not* ask much about this and use docs etc. instead but this is more about project practices
and also, if we're talking about the queues from a developer perspective, we should probably be on p6dev, not #perl6
... and this should be in p6dev... I only reacted here because of the commit message.
pmurias probably missed the existence of #p6dev?
github still says: payload URL: http://hack.p6c.org:8088/dalek?t=freenode,p6dev
[Coke]: I'll move it to p6dev
also, maybe ask on #p6dev? :)
#perl6 #perl6-release #p6dev #moarvm #perl6-toolchain I assume? :-)
mojca: see #p6dev, #perl6-release - 2016.03 rakudo will be uploaded today.
Should travis-ci be on #p6dev (if it's going to be anywhere)
I see #p6dev really as language and compiler development
shall DBIish's dalek output move to #p6dev, btw?
yeah, #p6dev :)
timotimo: perhaps we should continue this on #p6dev ?
CurtisOvidPoe_: At some point you might want to talk to people on #p6dev about what they're doing as that channel is more focused on development work.
....there is #p6dev?
http://irclog.perlgeek.de/p6dev
johnP: #p6dev is where the development discussion happens these days. We try to keep #perl6 for the users.
because #p6dev was split off
[Tux]: you probably want to post those numbers on #p6dev :-)
PSA: rakudo, nqp and roast commits will now be announced in #p6dev, not here anymore
I didn't know there was a #p6dev
moritz: you know better than i how to administrate dalek; i don't see #p6dev in botnix.conf; is that by accident?
hmmm.... so why is dalek still here and where is #p6dev ?
#p6dev !?!?
maybe #p6dev should be in the channel subject for the next few days or something
i also think that p6devs mostly do things right, which means that the impl is probably correct
p6devl: help!
I thought maybe p6devl forwarded to the perl6-dev mailing list. :)
that gets me closer to p6dev...