From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Nickolai Belakovski <nbelakovski@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Git List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (May 2019, #05; Thu, 30)
Date: Thu, 6 Jun 2019 15:09:06 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1906061508090.42@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <CAC05385iALWsN_fRS-Mzt1Q-3kV+562KfkV+Gz_XtEw40_ddLQ@mail.gmail.com>
Hi,
On Wed, 5 Jun 2019, Nickolai Belakovski wrote:
> On Thu, May 30, 2019 at 5:20 PM Junio C Hamano <gitster@pobox.com> wrote:
> >
> > * nb/branch-show-other-worktrees-head (2019-05-07) 3 commits
> > - branch: add worktree info on verbose output
> > - branch: update output to include worktree info
> > - ref-filter: add worktreepath atom
> >
> > "git branch --list" learned to show branches that are checked out
> > in other worktrees connected to the same repository prefixed with
> > '+', similar to the way the currently checked out branch is shown
> > with '*' in front.
> >
>
> I see that this has been in 'pu' for some time now. Is there something
> holding it up from going into 'next'?
If all that is needed is a vote in favor of this feature: Here is my
"yay!". I am a heavy user of worktrees, and this strikes me as something I
want to see in the output of `git branch --list`.
Thanks,
Johannes
prev parent reply other threads:[~2019-06-06 13:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 21:23 What's cooking in git.git (May 2019, #05; Thu, 30) Junio C Hamano
2019-05-31 11:39 ` Johannes Schindelin
2019-05-31 17:02 ` Junio C Hamano
2019-05-31 17:14 ` Johannes Schindelin
2019-05-31 12:42 ` Johannes Schindelin
2019-05-31 17:34 ` Junio C Hamano
2019-05-31 18:48 ` Johannes Schindelin
2019-06-01 15:08 ` Kaartic Sivaraam
2019-06-02 17:48 ` Philip Oakley
2019-05-31 18:56 ` Junio C Hamano
2019-05-31 20:26 ` cc/list-objects-filter-wo-sparse-path, was " Johannes Schindelin
2019-06-02 14:32 ` Jiang Xin
2019-06-05 18:38 ` Nickolai Belakovski
2019-06-06 13:09 ` Johannes Schindelin [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.1906061508090.42@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nbelakovski@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).