SVK::Command::Info(3)

💖 SVK::Command::Info — the vibe check for your files 💖

okay bestie, welcome to SVK::Command::Info(3) — part of the User Contributed Perl Documentation situation, and honestly? It's giving "tell me everything about this file or directory" energy. 🦋

---

✨ NAME ✨

SVK::Command::Info — Display information about a file or directory. That's it, that's the job. She's a simple girl with one purpose and she ate. 💅

---

🌸 SYNOPSIS 🌸

info [PATH | DEPOTPATH]...

So you just hand her a PATH or a DEPOTPATH — or like, several of them, she can multitask — and she spills all the tea. ✨

---

🎀 OPTIONS 🎀

• -R [--recursive] — descend recursively, bestie. Like, all the way down. 🌈

---

👑 DESCRIPTION 👑

Okay so, fr fr, here's the way to display the info of a checkout path:

% svk info ~/dev/svk
Checkout Path: /Users/gugod/dev/svk
Depot Path: //svk/local
Revision: 447
Last Changed Rev.: 447
Last Changed Date: 2006-11-28
Copied From: /svk/trunk, Rev. 434
Merged From: /svk/trunk, Rev. 445

So you can see the result has some basic information: the actual depot path, and current revision. Iconic, lowkey essential. ✨ Next up are the advanced deets about copy and merge source for this depot path — that's where it gets juicy. 🍓

The result of svk info //svk/local is almost the same as above, except for the Checkout Path: line is not there — because you are not referring to a checkout path. No checkout path, no checkout path line. She's consistent, she's fair. 💅

⚠️ bestie, pay attention, this part is important ⚠️

Note that the revision numbers on Copied From: and Merged From: lines are for the source path (//svk/trunk), not the target path (//svk/local). 😭 The example above state that, //svk/local is copied from the revision 434 of //svk/trunk, and //svk/local was merged from the revision 445 of //svk/trunk. Hence if you do a svk log -r 434 //svk/local, svk would tell you that //svk/local does not exist at revision 434. Not me getting confused by this the first time 🙈 — the numbers belong to the source, okay? Periodt.

So far there is no easy way to tell the actual revision number of //svk/local right after a copy or merge. 💀 That's just the situation. We don't make the rules.

If the target is a depot path, or the corresponding depot path of the target checkout path is actually a mirroring path, the output of this command will look like this:

% svk info //svk/trunk
Depot Path: //svk/trunk
Revision: 447
Last Changed Rev.: 445
Mirrored From: svn://svn.clkao.org/svk, Rev. 1744

So you can see this depot path is mirrored from a remote repository, and so far mirrored up to revision 1744. Slay. 🔥 Mirrored from svn://svn.clkao.org/svk, sitting pretty at Rev. 1744 — main character energy, honestly. 👑

---

💜 and that's the whole page, bestie! This lil masterpiece comes to you from perl v5.42.0, dated 2025-07-25, and it lives at SVK::Command::Info(3). Go forth and svk info responsibly. 🫶✨