Parrot 4.10.0 "[Red-eared Parakeet]" parrot.org/ | Log: irclog.perlgeek.de/parrot
Set by moderator on 21 November 2012.
00:05 Psyche^ joined 00:16 benabik joined 00:36 kid51 joined
kid51 Does anyone know how to re-open a closed Github issue? 00:37
I have gone to: github.com/parrot/parrot/issues
... clicked on the Reopen button ...
... and put a checkmark in the box next to Issue #882.
But I don't see any button like "Save Changes" or "Submit".
My intention is to re-open the ticket and take it. 00:38
msg benabik Yes, 'file parrot' gives me virtually identical results. That's useful for my purpose, albeit perhaps not portable to non-Unix. 00:39
aloha OK. I'll deliver the message.
00:40 benabik joined
benabik kid51: On the ticket page, I see "Reopen" next to "Comment" under the comment box. 00:40
kid51 benabik: That's where I certainly would *expect* it to be. But I don't have anything next to "Comment." 00:42
And, to anticipate the next question, yes, I am logged in. :-) 00:43
I wonder if this is happening because the commit was closed with a 'pull'.
The location bar is saying: "github.com/parrot/parrot/pull/882" 00:44
benabik It's because it's a pull request, which was closed by merging. Can't reopen because the required action has been taken. :-/ Conflation of pull request with issues is pesky. 00:45
kid51 If I go to a different Closed ticket -- one that was *not* closed by a merge/pull -- then I see "Reopen"
e.g. github.com/parrot/parrot/issues/873
kid51 never was in favor of moving to github for issue tracking, but ... 00:46
kid51 is not going to re-fight that battle
Well, in any event, it's on my personal TODO list.
afk for dinner
01:10 Reini joined 01:11 Mike-PerlRecruiter_ joined 02:18 kid51 joined 03:47 kid51 joined
Reini dukeleto: ok, when protoent is NULL we will return −1, okay? 04:18
benabik: I know of @executable_path which works on all darwin versions. @rpath is a bit more flexible because it does not need to create a special installable libparrot and executables. 04:19
you can have multiple -rpath's in every exe, so blib/lib and ../lib 04:20
04:25 davidfetter joined
Reini So our GC walks into the wrong direction: github.com/parrot/parrot/issues/880 04:31
It walks a work_list PMC from the parent thread interp 04:32
It should walk down, not up.
Who wrote the threads walker? 04:33
05:32 davidfetter joined 06:25 woosley joined 08:36 Reini joined 08:45 migimunz joined 08:52 migimunz2 joined 08:57 migimunz joined 09:36 Reini joined 09:50 tuxit joined 10:14 Reini joined 10:55 migimunz2 joined 11:14 Reini joined 11:19 migimunz joined 11:27 migimunz2 joined 11:32 migimunz joined 12:15 Reini joined 12:48 Reini joined 13:13 Mike-PerlRecruiter_ joined 13:49 Reini joined 14:05 Reini joined, contingencyplan joined 14:09 PacoAir joined 14:36 davidfetter joined 14:48 bluescreen joined 15:26 benabik joined 16:13 Reini joined 19:09 Reini joined 19:19 dmalcolm joined 20:45 dmalcolm_ joined 21:22 perlite joined 22:02 bluescreen joined 22:12 bluescreen_ joined 23:09 cooper joined 23:42 elmex joined 23:48 Reini joined