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: Thu, 04 Jun 2026 10:14:44 +0900 [thread overview]
Message-ID: <xmqqik7zp0mz.fsf@gitster.g> (raw)
In-Reply-To: <CAPGaHktHLPUeSuhETwyBo+jE2fMu40jHW284PN+2oY1YJ2j0Yw@mail.gmail.com> (Norbert Kiesel's message of "Wed, 3 Jun 2026 15:51:23 -0700")
"Kiesel, Norbert" <norbert.kiesel@creditkarma•com> writes:
> Hi Junio,
>
> I looked at the usage of `.git/description` and I could not find any
> usage. We do have
> Git branch descriptions which are stored in .git/config, but that does
> not seem to be
> usable to store the worktree description or the worktree creation timestamp.
>
> So are you ok if I send the PR again, just using "description" instead
> of "note"?
Not really. Not adding "note" and reusing "description" merely
removes one smaller problem I immediately see.
As I said a few times, I do not get why such a "feature" is needed.
Also, be it a "note" or "description", people notice typoes in the
message and go in to edit with their editor, which would update the
mtime of the file, so if that is the timestamp you are using for
anything real, I am not sure how well it would work in practice.
I'll let the others to figure out the merit of the feature and will
come back next week to see what concensus they reached.
Thanks.
prev parent reply other threads:[~2026-06-04 1:14 UTC|newest]
Thread overview: 6+ 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
2026-06-02 23:57 ` Junio C Hamano
2026-06-03 0:03 ` Kiesel, Norbert
2026-06-03 22:51 ` Kiesel, Norbert
2026-06-04 1:14 ` Junio C Hamano [this message]
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=xmqqik7zp0mz.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=norbert.kiesel@creditkarma$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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