From: Junio C Hamano <gitster@pobox.com>
To: "Kiesel, Norbert" <norbert.kiesel@creditkarma.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] worktree: record creation time and free-form note
Date: Wed, 03 Jun 2026 08:52:09 +0900 [thread overview]
Message-ID: <xmqq1peots9i.fsf@gitster.g> (raw)
In-Reply-To: <CAPGaHku+RAV+FA3C0md0xHiavfdB_anoqcMM06MAiU1VyMAdLA@mail.gmail.com> (Norbert Kiesel's message of "Tue, 2 Jun 2026 14:40:44 -0700")
"Kiesel, Norbert" <norbert.kiesel@creditkarma.com> writes:
> From 130cd5e4a25e6672b2a97268e1100b6ef03fa552 Mon Sep 17 00:00:00 2001
> From: Norbert Kiesel <norbert.kiesel@creditkarma.com>
> Date: Mon, 1 Jun 2026 17:03:39 -0700
> Subject: [PATCH] worktree: record creation time and free-form note
>
> Add per-worktree metadata so users can answer "what is this worktree
> for, and when did I make it?" without resorting to external notes.
Although I am not personally interested in this topic all that much,
let me point out that we have $GIT_DIR/description file that may be
useful for something like this. It has been the canonical place for
the main repository to identify itself long before secondary worktrees
were invented and $GIT_COMMON_DIR/worktrees/$worktree/description would
be a natural extension of the concept, I'd presume.
next prev parent reply other threads:[~2026-06-02 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 21:40 [PATCH] worktree: record creation time and free-form note Kiesel, Norbert
2026-06-02 23:52 ` Junio C Hamano [this message]
2026-06-02 23:57 ` Junio C Hamano
2026-06-03 0:03 ` Kiesel, Norbert
2026-06-03 22:51 ` Kiesel, Norbert
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=xmqq1peots9i.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=norbert.kiesel@creditkarma.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