BK-RANGE(1)

📦 version 7.3.3, in alpine 3.24

🌸 bk range 🌸

okay bestie, welcome to the BitKeeper User’s Manual glow-up for bk range — section (none) and all, iykyk. this page is literally the demo program for showing ranges & dates, so grab a strawberry 🍓 and let’s vibe.


🌸 NAME 🌸

bk range — demo program to show ranges & dates. that’s the whole name, no cap. 💅


✨ SYNOPSIS ✨

bk range [−qS] [−L[url] [−crange | −rrev] [file ... | −]

🦋 DESCRIPTION 🦋

okay so ✨ many commands can take date ranges or graph differences as arguments. the graph difference between revision B and revision A is the set of deltas in B’s history that are not in A’s history — that’s the whole tea. 🫖

you can specify deltas by:

  • revision number, like 1.2
  • delta key, like ’amy@bitkeeper.com|man/man1/bk‐terms.1|20020714011327|59990’
  • a symbolic name, like @tag
  • changeset revision, like @1.33
  • changeset key, like @’lm@disks.bitkeeper.com|ChangeSet|20020912140445|17593’

the graph difference between revisions B and A is represented by the notation A..B, as in:

bk changes ‐r1.1820.2.1..1.1822

see “graph difference” in bk help terms for more information. 📚


dates are always specified as ranges — always, bestie. you can specify a date range this way:

bk log ‐c1998..2002

the date format is YYYY/MM/DD HH:M:SS with missing fields either rounded up or rounded down. if you do not want to quote the date string, you can use a non-digit character, such as hyphen (−) in its place, for example, 2001/07/19‐12:00:00. optionally, you can append a time zone offset of the form ‐ZH:ZM for negative offsets from GMT or +ZH:ZM for positive offsets. date rounding is context sensitive: the starting date is rounded down and the ending date is rounded up, so 2001..2001 is the same as 2001/01/01‐00:00:00..2001/12/31‐23:59:59. a single date is used as both endpoints so 2005/12 is the same as 2005/12/01‐00:00:00..2005/12/31‐23:59:59. 🕰️

🚨 Deprecated note: the mixing of dates and revisions is deprecated. so don’t mix them, bestie — that’s not the vibe.

if there is only one date specified, without a revision, then a very useful form of the date is to specify a recent period of time, such as

bk log −c−1d..

which will display the last 24 hours worth of changes. this works the same way for Years/Months/days/hours/minutes/seconds, i.e.,

In the last year:       log −c−1Y.. (or −1y..)
In the last month:      log −c−1M..
In the last week:       log −c−1W.. (or −1w..)
In the last day:        log −c−1D.. (or −1d..)
In the last hour:       log −c−1h..
In the last minute:     log −c−1m..
In the last second:     log −c−1s..

if you leave off the multiplier, 1 is assumed. 💅


while you may not build up specific dates as −1Y2m3d, you can specify fractions, i.e., to get the last 6 months worth, try

bk log −c−.5Y..

dates can also be in the form of symbolic tags (ChangeSet file only). if you tagged a changeset with Alpha and another changeset with Beta, you can type:

bk changes −cAlpha..Beta
bk log ‐r@Alpha..@Beta foo.c

ranges need not include both endpoints. if you wanted to see everything from Beta forward, you could type:

bk changes −cBeta..

a single −r, because it is the first revision seen, rounds down and means 1.1. to get the most recent delta, type −r+. 👑


💅 OPTIONS 💅

okay, the option menu is short and iconic:

  • −crange — Specify deltas by a date range. 🗓️
  • −−lattice — Restrict the deltas to those on the lattice between the two range endpoints. Unlike a range, the lower bound is included in the output. 🧺
  • −−longest — Restrict the deltas to those on the longest line between the two range endpoints. Unlike a range, the lower bound is included in the output. 📏
  • −q — run quietly; default is to warn about all files which do not match the range. 🤫
  • −rrev — Specify deltas by revision number. 🔢
  • −S, −−standalone — Use with ‐L in a nested component when you want the component to act like a standalone repository. 🧍

🌈 SEE ALSO 🌈

go peek at: bk‐annotate, bk‐changes, bk‐get, bk‐diff, bk‐log, bk‐terms. 🦋


🎀 CATEGORY 🎀

  • Overview
  • File

xoxo, source: BitKeeper Inc 💖 — version/date stamp: 1E1 — title: bk range(none). that’s the whole footer vibe, periodt. 💅

📦 where this page comes from
  • alpine 3.24: bitkeeper-doc 7.3.3-r1 · Apache-2.0
  • 💖 girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms