From: "Rubén Justo" <rjusto@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: rj/branch-unborn-in-other-worktrees (was Re: What's cooking in git.git (Apr 2023, #05; Mon, 17))
Date: Wed, 19 Apr 2023 22:24:23 +0200 [thread overview]
Message-ID: <3fa2ad13-9056-a14f-6d80-0f8f6c23597d@gmail.com> (raw)
In-Reply-To: <xmqqfs8xfw25.fsf@gitster.g>
On 18/4/23 10:12, Junio C Hamano wrote:
> * rj/branch-unborn-in-other-worktrees (2023-03-27) 5 commits
> - branch: avoid unnecessary worktrees traversals
> - branch: rename orphan branches in any worktree
> - branch: description for orphan branch errors
> - branch: use get_worktrees() in copy_or_rename_branch()
> - branch: test for failures while renaming branches
>
> Error messages given when working on an unborn branch that is
> checked out in another worktree have been improved.
>
> Will merge to 'next'?
> source: <f8e6447e-5cd3-98fa-f567-39e1c60dacb0@gmail.com>
The current version of this series has not received any comments. However,
the previous version was already merged to 'next', although it was kicked
out due to some unwanted behaviors that were detected. Which have been
fixed in the current version.
I missed the "Will merge to 'next'?" for the previous version. I just want
to say that I'm still happy with the current one.
Thank you.
prev parent reply other threads:[~2023-04-19 20:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 8:12 What's cooking in git.git (Apr 2023, #05; Mon, 17) Junio C Hamano
2023-04-18 14:53 ` tb/pack-revindex-on-disk (was: Re: What's cooking in git.git (Apr 2023, #05; Mon, 17)) Taylor Blau
2023-04-18 14:54 ` tb/enable-cruft-packs-by-default " Taylor Blau
2023-04-18 14:56 ` tb/ban-strtok " Taylor Blau
2023-04-18 16:58 ` tb/ban-strtok Junio C Hamano
2023-04-18 19:31 ` tb/ban-strtok Taylor Blau
2023-04-19 2:51 ` en/header-split-cache-h (Was Re: What's cooking in git.git (Apr 2023, #05; Mon, 17)) Elijah Newren
2023-04-19 20:24 ` Rubén Justo [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=3fa2ad13-9056-a14f-6d80-0f8f6c23597d@gmail.com \
--to=rjusto@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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;
as well as URLs for NNTP newsgroup(s).