parv

• About: Ranting, blurbing about Perl, among other things.

Recent Actions

• Posted Parsing of anime reviews on rec.arts.anime.misc to parv

  I have been collecting posts from rec.arts.anime.misc newsgroup, mostly related to anime reviews to prioritize which one to see. The format is more or less the same of (collection of) reviews ...

  • title
  • a paragraph of comments
  • ending with some kind of quality statetmen…

• Commented on Re: Need IO::Pty help with *BSD/OSX
  (Amazing I was able to post a reply this time!)...
• Commented on Re: Need IO::Pty help with *BSD/OSX
  Thanks, gvl. I did expect that bc might have changed and/or you might be running FreeBSD newer than 8. But that thought came to me after having published the post/reply....
• Posted Re: Need IO::Pty help with *BSD/OSX to parv

  (I was having problem of "session timeout" after submitting the following comment. So here it is instead being a reply at Need IO::Pty help with *BSD/OSX)

  I had no problem with /usr/bin/bc test on Fr…

• Commented on Got CSS to hide ridiculously long posts?
  It Works! I am very grateful to you for restoring calm....
• Posted Got CSS to hide ridiculously long posts? to parv

  Does anybody have CSS handy to hide -- say anything after 2 paragraphs -- ludicrously long posts on the front page of blogs.perl.org?

• Commented on Publicly accessible archive of perl security advisories?
  Ha! My query was quite a duplicate of brian d f's; I should have searched blogs.perl too before posting. Thanks much....
• Posted Publicly accessible archive of perl security advisories? to parv

  There seems to be no announcement/read-only public mailing list archive related to perl security issues, unlike freebsd-announce@freebsd for example. Is there a publicly accessible URL where past (perl security) advisories…

• Commented on Patch known perlcore ptr problems
  Would security advisories be issued for any of the issues?...
• Commented on When to create a branch in Git?
  Aristotle, actually your reply reminded me of the occasional problem that sometimes come with reset --hard and related avoidance procedure. I will change my way of hard reset to reference update. Thank you....
• Posted git related bourne-like shell functions to parv

  Wanted to post git related shell functions, so they are now at PerlMonks.

• Commented on When to create a branch in Git?
  About moving "master" back to "origin" ... # On master branch. git reset --hard point-to-move-to Is git reset --hard any more different than git branch -f ... above?...

Comment Threads

• Tim Bunce commented on Patch known perlcore ptr problems

  For the record, since the post has been edited now so the comments can't be seen in context, the original post said:

  For sysadmins: Please do not install 5.14.3, still avoid 5.16 at all. For downstream packagers: Please do not provide 5.14.3 without the needed security patches.

  Also, for the record, here's a summary of the outcome:

  Ok, so the final tally for the three new 5.14.3 critical security bugs appears to be:

  …

• Mark Leighton Fisher commented on When to create a branch in Git?

  Finally got the internal release out (in the low 300s for the commits). Hurts when I do that -- going to start branching.

  I can truly recommend "Version Control with Git" (the bat book) even though I haven't finished it yet -- my mental model of what I've read so far is clear (whereas before it was at best translucent, even after reading "Git Magic" and "Git for Computer Scientists").

  Thanks for all the great comments, BTW.

• educated_foo commented on Got CSS to hide ridiculously long posts?

  Simply posting replies to Famous Perl Luminaries (a.k.a. "brian d foy" (or am I messing up some punctuation?)) seems to fix the issue, though he deletes the replies.

• brian d foy commented on Got CSS to hide ridiculously long posts?

  Heh. I typically delete comments once I fix the "bug" they are reporting. I didn't think the second gist would make it past the MT cut-off.

• Reini Urban commented on Patch known perlcore ptr problems

  Thanks Tim for the comment with the revisions.

  I still stand to the recommendation against 5.16 at all. The reasons were posted on p5p, without any reaction. \0 in names are unprotected and exploitable. The whole new GV api with len is wrong. There can be no \0 in names and there should be none.