home.social

Search

483 results for “lukeshu”

  1. @lukeshu

    You're the only name in the log. (-:

    git.parabola.nu/abslibre.git/t

    I'm just giving the packagers (those that I know about and are easily contactable, at any rate) a tap on the shoulder before the rest of the world explicitly learns that #redo 1.5 is up.

    jdebp.uk/Softwares/redo/

    (Po-Chuan Hsieh of #FreeBSD is still using a URL that has not worked since Brexit. 17 million people voted that I should not have my domain name. (-:)

    @schmonz

    #djbwares 10 is next.

  2. @lukeshu

    You're the only name in the log. (-:

    git.parabola.nu/abslibre.git/t

    I'm just giving the packagers (those that I know about and are easily contactable, at any rate) a tap on the shoulder before the rest of the world explicitly learns that #redo 1.5 is up.

    jdebp.uk/Softwares/redo/

    (Po-Chuan Hsieh of #FreeBSD is still using a URL that has not worked since Brexit. 17 million people voted that I should not have my domain name. (-:)

    @schmonz

    #djbwares 10 is next.

  3. @lukeshu

    You're the only name in the log. (-:

    git.parabola.nu/abslibre.git/t

    I'm just giving the packagers (those that I know about and are easily contactable, at any rate) a tap on the shoulder before the rest of the world explicitly learns that #redo 1.5 is up.

    jdebp.uk/Softwares/redo/

    (Po-Chuan Hsieh of #FreeBSD is still using a URL that has not worked since Brexit. 17 million people voted that I should not have my domain name. (-:)

    @schmonz

    #djbwares 10 is next.

  4. @lukeshu

    You're the only name in the log. (-:

    git.parabola.nu/abslibre.git/t

    I'm just giving the packagers (those that I know about and are easily contactable, at any rate) a tap on the shoulder before the rest of the world explicitly learns that #redo 1.5 is up.

    jdebp.uk/Softwares/redo/

    (Po-Chuan Hsieh of #FreeBSD is still using a URL that has not worked since Brexit. 17 million people voted that I should not have my domain name. (-:)

    @schmonz

    #djbwares 10 is next.

  5. @lukeshu

    You're the only name in the log. (-:

    git.parabola.nu/abslibre.git/t

    I'm just giving the packagers (those that I know about and are easily contactable, at any rate) a tap on the shoulder before the rest of the world explicitly learns that #redo 1.5 is up.

    jdebp.uk/Softwares/redo/

    (Po-Chuan Hsieh of #FreeBSD is still using a URL that has not worked since Brexit. 17 million people voted that I should not have my domain name. (-:)

    @schmonz

    #djbwares 10 is next.

  6. It would be hard to overstate how much work it took to make this 4-line commit possible git.lukeshu.com/sbc-harness/co

    #9p
  7. OK, I've added 1e1 conversions to github.com/LukeShu/inferno-man . And so I've emailed the cat-v.org mailing list about those maybe being better than what's currently on man.cat-v.org

    #catv #InfernoOS #retrocomputing #archival

  8. OK, I've added 1e1 conversions to github.com/LukeShu/inferno-man . And so I've emailed the cat-v.org mailing list about those maybe being better than what's currently on man.cat-v.org

  9. OK, I've added 1e1 conversions to github.com/LukeShu/inferno-man . And so I've emailed the cat-v.org mailing list about those maybe being better than what's currently on man.cat-v.org

    #catv #InfernoOS #retrocomputing #archival

  10. OK, I've added 1e1 conversions to github.com/LukeShu/inferno-man . And so I've emailed the cat-v.org mailing list about those maybe being better than what's currently on man.cat-v.org

    #catv #InfernoOS #retrocomputing #archival

  11. Yesterday:
    - Got the nspawn FUSE PR to pass CI (…but it's failing again now‽)
    - Benchmark json patches github.com/flori/json/pull/567 …"interesting" change in baseline variance since April

    Today:
    - Respond to feedback on the nspawn PR
    - Feel spent, figure unstructured work will turn into something productive.… not so far

    Other:
    - Bugs on lukeshu.com/imworkingon/ 😞

  12. So I'm working on upgrading 's . But the ARM build takes forever and so my iteration time on solving problems is slow.

    In the course of this I've found some bugs in fosstodon.org/@lukeshu/1130699 I'm working around them by disabling affected tests if we're running in a qemu chroot. After I get the bew Ruby out, I'll look into fixing the Qemu bugs... but IDK how I'm going to prioritize that against other existing work.

  13. Yesterday:
    - Between the power being out & my brain being broken, not much

    Today:
    - Updated lukeshu.com/imworkingon/ to get "last updated" for pipermail mailinglist archives
    - Wrote some notes on email message threading lukeshu.com/blog/message-threa
    - Wrote a bit at lukeshu.com/imworkingon/ about why this week's work on is important.

    If any of this seems useful or important to you, plz consider throwing a few dollars my way lukeshu.com/sponsor/

  14. #DailyStandup

    Yesterday:
    - Between the power being out & my brain being broken, not much

    Today:
    - Updated lukeshu.com/imworkingon/ to get "last updated" for pipermail mailinglist archives
    - Wrote some notes on email message threading lukeshu.com/blog/message-threa
    - Wrote a bit at lukeshu.com/imworkingon/ about why this week's work on #GNU #binutils is important. #supply_chain_attack

    If any of this seems useful or important to you, plz consider throwing a few dollars my way lukeshu.com/sponsor/

  15. #DailyStandup

    Yesterday:
    - Between the power being out & my brain being broken, not much

    Today:
    - Updated lukeshu.com/imworkingon/ to get "last updated" for pipermail mailinglist archives
    - Wrote some notes on email message threading lukeshu.com/blog/message-threa
    - Wrote a bit at lukeshu.com/imworkingon/ about why this week's work on #GNU #binutils is important. #supply_chain_attack

    If any of this seems useful or important to you, plz consider throwing a few dollars my way lukeshu.com/sponsor/

  16. #DailyStandup

    Yesterday:
    - Between the power being out & my brain being broken, not much

    Today:
    - Updated lukeshu.com/imworkingon/ to get "last updated" for pipermail mailinglist archives
    - Wrote some notes on email message threading lukeshu.com/blog/message-threa
    - Wrote a bit at lukeshu.com/imworkingon/ about why this week's work on #GNU #binutils is important. #supply_chain_attack

    If any of this seems useful or important to you, plz consider throwing a few dollars my way lukeshu.com/sponsor/

  17. What I did yesterday, what I'm hopefully wrapping up today:

    - Tracking down where all of the bundled files in came from, and writing tooling to keep track of them: fosstodon.org/@lukeshu/1125671

  18. #DailyStandup

    - Because I was wanting to borrow some code from it, I fixed bitrot in git.lukeshu.com/2git/cvtutf-ma which is the scripts that make the git.lukeshu.com/2git/cvtutf repo, which is the history of the CVTUTF #Unicode library. #SoftwareArcheology

  19. - Because I was wanting to borrow some code from it, I fixed bitrot in git.lukeshu.com/2git/cvtutf-ma which is the scripts that make the git.lukeshu.com/2git/cvtutf repo, which is the history of the CVTUTF library.

  20. @lukeshu @amerl I found this article about using graphviz to generate "pointcrawls". slyflourish.com/pointcrawls.ht

  21. @schmonz @lukeshu

    I actually looked for contact details for Po-Chuan Hsieh, for the FreeBSD port, so that I could let xem know how messed up that port was; as I noted before. But there's only a wildly (a decade) out of date LinkedIn listing and an opaque FreeBSD account.

    The Parabola packaging of redo is several versions out of date, and has the pre-pre-Brexit URLs. Arch is on 1.4 at least but using the pre-Brexit URLs.

    I don't even know about Void, Hyperbola, et al.

    #redo #djbwares #nosh

  22. @schmonz @lukeshu

    I actually looked for contact details for Po-Chuan Hsieh, for the FreeBSD port, so that I could let xem know how messed up that port was; as I noted before. But there's only a wildly (a decade) out of date LinkedIn listing and an opaque FreeBSD account.

    The Parabola packaging of redo is several versions out of date, and has the pre-pre-Brexit URLs. Arch is on 1.4 at least but using the pre-Brexit URLs.

    I don't even know about Void, Hyperbola, et al.

    #redo #djbwares #nosh

  23. @schmonz @lukeshu

    I actually looked for contact details for Po-Chuan Hsieh, for the FreeBSD port, so that I could let xem know how messed up that port was; as I noted before. But there's only a wildly (a decade) out of date LinkedIn listing and an opaque FreeBSD account.

    The Parabola packaging of redo is several versions out of date, and has the pre-pre-Brexit URLs. Arch is on 1.4 at least but using the pre-Brexit URLs.

    I don't even know about Void, Hyperbola, et al.

    #redo #djbwares #nosh

  24. @schmonz @lukeshu

    I actually looked for contact details for Po-Chuan Hsieh, for the FreeBSD port, so that I could let xem know how messed up that port was; as I noted before. But there's only a wildly (a decade) out of date LinkedIn listing and an opaque FreeBSD account.

    The Parabola packaging of redo is several versions out of date, and has the pre-pre-Brexit URLs. Arch is on 1.4 at least but using the pre-Brexit URLs.

    I don't even know about Void, Hyperbola, et al.

    #redo #djbwares #nosh

  25. @schmonz @lukeshu

    I actually looked for contact details for Po-Chuan Hsieh, for the FreeBSD port, so that I could let xem know how messed up that port was; as I noted before. But there's only a wildly (a decade) out of date LinkedIn listing and an opaque FreeBSD account.

    The Parabola packaging of redo is several versions out of date, and has the pre-pre-Brexit URLs. Arch is on 1.4 at least but using the pre-Brexit URLs.

    I don't even know about Void, Hyperbola, et al.

    #redo #djbwares #nosh

  26. @schmonz @lukeshu

    I think that you possibly hadn't noticed before because it wasn't NetBSD; but now I've ported all three of #redo, #djbwares, and #nosh to NetBSD (testing on a non-amd64 architecture, no less!), as you've probably seen over the past few months. So now there's a system for building #NetBSD packages alongside Debian's, FreeBSD's, and OpenBSD's.

  27. @schmonz @lukeshu

    I think that you possibly hadn't noticed before because it wasn't NetBSD; but now I've ported all three of #redo, #djbwares, and #nosh to NetBSD (testing on a non-amd64 architecture, no less!), as you've probably seen over the past few months. So now there's a system for building #NetBSD packages alongside Debian's, FreeBSD's, and OpenBSD's.

  28. @schmonz @lukeshu

    I think that you possibly hadn't noticed before because it wasn't NetBSD; but now I've ported all three of #redo, #djbwares, and #nosh to NetBSD (testing on a non-amd64 architecture, no less!), as you've probably seen over the past few months. So now there's a system for building #NetBSD packages alongside Debian's, FreeBSD's, and OpenBSD's.

  29. @schmonz @lukeshu

    I think that you possibly hadn't noticed before because it wasn't NetBSD; but now I've ported all three of #redo, #djbwares, and #nosh to NetBSD (testing on a non-amd64 architecture, no less!), as you've probably seen over the past few months. So now there's a system for building #NetBSD packages alongside Debian's, FreeBSD's, and OpenBSD's.