SVK::Notify(3)

💖 NAME 💖

SVK::Notify — the little entry-status notification bestie of svk ✨

Like, it's literally right there in the name: svk entry status notification. That's the whole vibe. 🦋

---

🎀 SYNOPSIS 🎀

    $notify = SVK::Notify->new;
    $notify->node_status ('foo/bar', 'M');
    $notify->prop_status ('foo/bar', 'M');
    $notify->hist_status ('foo/bar', '+',
        'file://home/foo/.svk/local/trunk/bar', 13);
    $notify->node_baserev ('foo/bar', 42);
    $notify->flush ('foo/bar');
    $notify->flush_dir ('foo');

okay so this is the whole group chat, right here 👆 you spin up a notifier with SVK::Notify->new, then you just keep feeding it tea about what's happening to your entries. node_status, prop_status, hist_status, node_baserev — all the gossip — and then flush or flush_dir to actually let it out into the world. slay. 💅

---

🌸 DESCRIPTION 🌸

So like… the DESCRIPTION section on this page is genuinely empty. Not me being mysterious, not me gatekeeping — that's just what the page says. Nothing there. Zero. Nada. 🙈

What we do have is the synopsis up there, and honestly it's giving everything it needs to give: you make the object, you hand it status updates for paths, and you flush them. That's the whole arc. main character energy, minimal dialogue. 👑

no cap: if you want the deep lore, the synopsis is the lore. this page is a short one and that's iconic of it. ✨

---

so yeah — that's SVK::Notify, entry status notification, right from the User Contributed Perl Documentation crew, manual page SVK::Notify(3). 🫶

and a lil sign-off for the girlies keeping receipts: this was perl v5.42.0, dated 2025-07-25, page SVK::Notify(3). 🎀 bye bestie, go notify somebody 💜