BK-SET(1)

💅 bk set — set operations, but make it iconic ✨

bk set(none) — BitKeeper User's Manual — bk set(none)

okay so bestie, welcome to bk set — it's giving main character utility energy because this thing does set operations on a BitKeeper file and honestly? It ate. 💅

---

✨ SYNOPSIS ✨

---

🌸 DESCRIPTION 🌸

The bk set command performs set operations on a BitKeeper file. It's literally that girl — it provides these set operations: union, intersection, difference and symmetric difference. And if that wasn't enough, it also gives you the member function (is this element a member of the set?) plus the list function (list all sets which contain this member). No cap, it does it all. 👑

If the file is not specified, it defaults to the ChangeSet file. Periodt.

---

🎀 OUTPUT OPTIONS 🎀

Default output is a list of revisions, one per line. You can restrict output to only tagged revisions, and you can force it into revision, tag, or key format. But listen — only the ChangeSet file may have tags, which means combining tag output format with a regular file has unexpected results. Consider yourself warned, bestie. 😭

• -k — list all answers as keys, not as tags or revisions.
• -n — prefix each output line with the filename, like ChangeSet|1.3, so the output can be fed to other programs (yes, like bk log) — iykyk.
• -t — list all answers as tags where possible, else revisions.
• -tt — list only those answers which are tagged, and list them as the tag not the revision.
• -tr — list only those answers which are tagged, but list them as revisions.
• -tk — list only those answers which are tagged, but list them as keys.

---

🦋 SPECIFYING SETS 🦋

If a revision is specified for a set argument, the set is the set of deltas which make up that revision. Example: in a simple history without branches, revision 1.5 implies the set {1.1, 1.2, 1.3, 1.4, 1.5}. Slay.

A revision may be specified as a revision, as a symbolic tag, or as a BitKeeper key. It may also be specified as a -, for the second set only, in which case it expects a list of revisions (or keys) on stdin, one per line. 🫶

---

🌈 SET OPERATIONS 🌈

💖 UNION (setA | setB)

bk set [output opts] −o setA setB [file]

The union operation — familiar to programmers as a "bitwise or" — lists all members which occur in either set. It's giving "everyone's invited to the function." 🎉

🌸 INTERSECTION (setA & setB)

bk set [output opts] −a setA setB [file]

The intersection operator — familiar to programmers as a "bitwise and" — lists all members which occur in both sets. Only the real ones make the cut. ✨

🦋 DIFFERENCE (˜setA & setB)

bk set [output opts] −d setA setB [file]

The difference operator lists all members in setB which are not in setA. This is the most useful of the set operations — lowkey the goat — see the examples below. 👑

🧚 SYMMETRIC DIFFERENCE (setA ˆ setB)

bk set [output opts] −x setA setB [file]

The symmetric difference operator — familiar to programmers as an "exclusive or" — lists all members which occur in only one of the two sets. It's giving "you can sit with us but only if you're not already at the other table." 💀

⭐ ELEMENT

bk set [output opts] −e −rrev setA [file]

The element operator treats the specified revision as a single element, not as an implied set, and lists the element if it is in the set. Vibe check: are you in or are you out? 💅

🍓 LIST

bk set −l −rrev [file]

The list operator treats the specified revision as a single element, not as an implied set, and lists all sets (as revisions) which contain the element as part of their set. It's typically used to see if a bug fix is in a particular release. Ngl, this is iconic for release tracking.

Heads up bestie: If the changeset has been excluded from a later changeset, the later changeset and its descendants will not be listed. 😭

💜 SET

bk set −s −rrev [file]

The set operator treats the specified revision as a set, and lists all elements of that set. It's giving "show me everything in your group chat." 🌈

---

👑 NESTED 👑

The set command will look at the product changeset file by default. Periodt.

• -S — perform the set operation on the current component.

---

🔥 EXAMPLES 🔥

A good use of this command is the generation of release notes. To do so, pick the starting and ending points and do this:

$ bk set ‐d ‐rbk‐2.0 ‐rbk‐2.0.1 | bk changes ‐
ChangeSet@1.1425.5.19, 2001‐10‐12 15:18:06, lm@work
  utils.c:
    Remove debugging.
    Sleep 50 milliseconds when waiting for the lock.

ChangeSet@1.1425.5.20, 2001‐10‐15 15:57:42, lm@disks
  A weekend’s worth of testing of locking over NFS
  turned into this cset.

ChangeSet@1.1425.5.21, 2001‐10‐16 08:35:26, lm@disks
  The cset lock was too fine grained.
  This is a short term fix,
  the longer term fix is the per file locking
  Andrew is working on.
  TAG: bk‐2.0.1

To see the tagged releases which contain bk‐2.0.3:

$ bk set ‐l ‐tt ‐rbk‐2.0.3
bk‐2.0.3
bk‐2.0.4
bk‐2.0.4b
bk‐2.1.2
bk‐2.1.3
bk‐3par_merge
bk‐3par_merge2

---

🎀 SEE ALSO 🎀

bk‐changes, bk‐log

---

🌟 CATEGORY 🌟

Utility

---

💖 okay that's the whole vibe, bestie. This page is brought to you by BitKeeper Inc — 1E1 — bk set(none). Go slay those set operations. 🫶✨🎀