From: Junio C Hamano <gitster@pobox.com>
To: Nickolai Belakovski <nbelakovski@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2019, #04; Wed, 20)
Date: Wed, 20 Mar 2019 13:56:50 +0900 [thread overview]
Message-ID: <xmqqva0euorx.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <xmqqa7hqw844.fsf@gitster-ct.c.googlers.com> (Junio C. Hamano's message of "Wed, 20 Mar 2019 12:13:47 +0900")
Junio C Hamano <gitster@pobox.com> writes:
> * nb/branch-show-other-worktrees-head (2019-03-18) 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.
>
> The top one probably deserves retitling.
> The second one is of dubious value, but if we are keeping it,
> it should also be retitled.
Sorry, but my commentary in the last paragraph is stale. These
patches have been updated with more sensible titles (as we can see
from the recent date for the topic). I've moved this topic out of
Stalled section back to Cooking section.
next prev parent reply other threads:[~2019-03-20 4:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 3:13 What's cooking in git.git (Mar 2019, #04; Wed, 20) Junio C Hamano
2019-03-20 4:56 ` Junio C Hamano [this message]
2019-03-20 11:23 ` Thomas Gummerer
2019-03-20 22:05 ` Rohit Ashiwal
2019-03-20 22:56 ` Thomas Gummerer
2019-03-20 23:07 ` Rohit Ashiwal
2019-03-21 0:31 ` Junio C Hamano
2019-03-20 22:42 ` Ævar Arnfjörð Bjarmason
2019-03-21 0:46 ` Junio C Hamano
2019-03-21 5:19 ` Junio C Hamano
2019-03-21 9:13 ` Ævar Arnfjörð Bjarmason
2019-03-21 9:46 ` Junio C Hamano
2019-03-21 10:37 ` Ævar Arnfjörð Bjarmason
2019-03-21 11:14 ` Duy Nguyen
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=xmqqva0euorx.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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).