All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Norbert Kiesel <nkiesel@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Feature request: support listing worktrees sorted by creation time
Date: Thu, 05 Mar 2026 07:50:54 -0800	[thread overview]
Message-ID: <xmqqqzpy46n5.fsf@gitster.g> (raw)
In-Reply-To: <CAM+g_Nt8vZX4NxPvddJxNvSRgdMWQaLg2O9xzAU1pTHa=Et-gw@mail.gmail.com> (Norbert Kiesel's message of "Wed, 4 Mar 2026 23:14:41 -0800")

Norbert Kiesel <nkiesel@gmail.com> writes:

> I have multiple repos with more than 20 worktrees, and sometimes
> forget the name of a recently added worktree. Therefore it would
> really be nice if I could use something like ‘git worktree list
> —created’ to list them by their creation timestamp. Is that something
> that makes sense to you as well? I could also create a pull request
> for this if you would like it.

I do not think we have any _record_ of when each of these worktrees
was created, so this is not a realistic request.

The output from "git worktree list" may be more than 20 lines, but
isn't your terminal taller than 20 lines ;-)?

Since very early days of Git, we have created .git/description file
that is not used very much (I think it is shown in gitweb).  Perhaps
worktree should have an equivalent in per-worktree part of their
.git/ directory and "git worktree list --verbose" can use its
contents in addition to the additional pieces information it already
shows, or something like that, perhaps?

  parent reply	other threads:[~2026-03-05 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05  7:14 Feature request: support listing worktrees sorted by creation time Norbert Kiesel
2026-03-05  7:35 ` Johannes Sixt
2026-03-05  7:41   ` Norbert Kiesel
2026-03-05 15:50 ` Junio C Hamano [this message]
2026-03-05 23:36   ` Norbert Kiesel
2026-03-06 13:02   ` Erik Cervin Edin

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=xmqqqzpy46n5.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=nkiesel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.