From: Christian Weisgerber <naddy@mips.inka.de>
Subject: Lost among the branches
To: gameoftrees@openbsd.org
Date: Mon, 15 May 2023 17:37:27 +0200

I have found a new toy to probe the limits of GoT:
https://github.com/mozilla/gecko-dev

I would like to update my worktree to a commit found somewhere in
the convoluted (merge, merge) history of the current branch:

  $ cd gecko-dev
  $ got br
  release
  $ got log -b -S FIREFOX_112_0_RELEASE
  -----------------------------------------------
  commit 51aeebd8221e07415c275453ebe88cce39e151ce
  from: Mozilla Releng Treescript <release+treescript@mozilla.org>
  date: Tue Apr 11 12:40:50 2023 UTC
   
   No bug - Tagging d2b2ff2c6e3ceb267e77b0163c860f7a1f13ff4a with FIREFOX_112_0_RELEASE a=release CLOSED TREE DONTBUILD
   
  $ got up -c 51aeebd8221e07415c275453ebe88cce39e151ce
  got: work tree's head reference now points to a different branch; new head reference and/or update -b required

Aaand I'm lost.  What now?  The commit is in the branch's history,
so why can't I go there?  update -b <what>??

-- 
Christian "naddy" Weisgerber                          naddy@mips.inka.de