Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Julia Evans <julia@jvns.ca>
Cc: "D. Ben Knoble" <ben.knoble@gmail.com>,
	 Julia Evans via GitGitGadget <gitgitgadget@gmail.com>,
	 git@vger.kernel.org,
	 Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Subject: Re: [PATCH v4] doc: checkout: rewrite detached HEAD state explanation
Date: Fri, 13 Nov 2026 17:54:49 -0800	[thread overview]
Message-ID: <xmqq8q2w89ee.fsf@gitster.g> (raw)
In-Reply-To: <a70524b5-5ece-49fd-acd5-c97e21faa76d@jvns.ca> (Julia Evans's message of "Fri, 13 Nov 2026 12:57:56 -0500")

Julia Evans <julia@jvns.ca> writes:

> Okay. How about this?  (the added sentence is between the **)
>
>    For example, a data scientist could use this to run an old version of a
>    data pipeline or a programmer could use this to figure out when a bug
>    was introduced. **You can also use this to make experimental commits
>    without being on a branch.** By detaching `HEAD`, you don't need to
>    create a temporary branch.

Yes, taking the "data scientist" example as a "pure time machine
without touching, just observing" scenario, and the "programmer"
example as an "inspect and experiment" scenario, the addition of
this single sentence is sufficient to hint at the wide range of
usefulness to which this feature applies.  Nicely done.

I think this is short and thin enough to be good material to be
shared between the manual for everybody (which would want to cover
wider workflows with possibly thin coverage on some and thorough
coverage on others) and a survival guide for those who are lost
(which can be more targeted towards specific audiences).

  parent reply	other threads:[~2026-11-14  1:54 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 14:52 [PATCH] doc: checkout: rewrite detached HEAD state explanation Julia Evans via GitGitGadget
2026-10-07 16:43 ` Junio C Hamano
2026-10-13 12:54   ` Julia Evans
2026-10-19 14:05   ` Julia Evans
2026-10-19 21:24     ` Junio C Hamano
2026-10-20 12:52       ` Julia Evans
2026-10-20 13:06         ` Julia Evans
2026-10-07 19:02 ` Kristoffer Haugsbakk
2026-10-13 11:48   ` Julia Evans
2026-10-13 12:20     ` Kristoffer Haugsbakk
2026-10-13 12:27       ` Julia Evans
2026-10-13 12:42         ` Julia Evans
2026-10-13 13:01 ` [PATCH v2] " Julia Evans via GitGitGadget
2026-10-14 18:52   ` Junio C Hamano
2026-10-14 21:10     ` Julia Evans
2026-10-15 20:58 ` [PATCH v3] " Julia Evans via GitGitGadget
2026-10-15 22:39   ` Junio C Hamano
2026-10-16 14:55     ` Julia Evans
2026-10-16 17:03       ` Junio C Hamano
2026-10-16 18:35         ` Julia Evans
2026-10-16 19:05           ` Junio C Hamano
2026-10-16 19:03 ` [PATCH v4] " Julia Evans via GitGitGadget
2026-10-16 21:10   ` Junio C Hamano
2026-11-07 20:06     ` D. Ben Knoble
2026-11-08  4:25       ` Junio C Hamano
2026-11-09 21:48         ` Julia Evans
2026-11-10  6:46           ` Junio C Hamano
2026-11-10 13:13             ` Julia Evans
2026-11-11 21:45       ` Julia Evans
2026-11-12  1:58         ` Ben Knoble
2026-11-12 15:40         ` Junio C Hamano
2026-11-12 16:37           ` Julia Evans
2026-11-12 19:25             ` Junio C Hamano
2026-11-12 22:45               ` Julia Evans
2026-11-13  2:25                 ` Junio C Hamano
2026-11-13 12:45                   ` Julia Evans
2026-11-13 17:23                     ` Junio C Hamano
2026-11-13 17:57                       ` Julia Evans
2026-11-13 18:43                         ` Julia Evans
2026-11-14  1:54                         ` Junio C Hamano [this message]
2026-11-14  2:28                           ` Julia Evans
2026-11-13 19:49                       ` Julia Evans
2026-11-13 21:56                         ` Junio C Hamano
2026-11-13 22:17                           ` Julia Evans
2026-10-16 22:02   ` Junio C Hamano
2026-11-11 21:34 ` [PATCH v5] " Julia Evans via GitGitGadget
2026-11-11 23:14   ` Junio C Hamano
2026-11-12  0:01     ` Julia Evans
2026-11-12  4:08     ` Junio C Hamano
2026-11-12 22:47 ` [PATCH v6] " Julia Evans via GitGitGadget

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq8q2w89ee.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=julia@jvns.ca \
    --cc=kristofferhaugsbakk@fastmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox