From: "Rubén Justo" <rjusto@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2023, #06; Thu, 27)
Date: Sun, 30 Jul 2023 03:35:33 +0200 [thread overview]
Message-ID: <3267d00f-d7b7-1288-108c-21823265d854@gmail.com> (raw)
In-Reply-To: <xmqqh6po95a5.fsf@gitster.g>
> * jc/branch-in-use-error-message (2023-07-21) 1 commit
> - branch: update the message to refuse touching a branch in-use
>
> "git branch -f X" to repoint the branch X seid that X was "checked
> out" in another worktree, even when branch X was not and instead
> being bisected or rebased. The message was reworded to say the
> branch was "in use".
>
> Will merge to 'next'?
> source: <xmqqr0p1szhz.fsf_-_@gitster.g>
I think, this is a good refinement of the message to describe an
implicitly checked out branch. Therefore, no objection to merge it to
next.
next prev parent reply other threads:[~2023-07-30 1:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 1:46 What's cooking in git.git (Jul 2023, #06; Thu, 27) Junio C Hamano
2023-07-28 2:13 ` Jacob Abel
2023-07-28 5:11 ` Junio C Hamano
2023-07-30 1:35 ` Rubén Justo [this message]
2023-07-31 16:29 ` tb/commit-graph-tests (was: Re: What's cooking in git.git (Jul 2023, #06; Thu, 27)) Taylor Blau
2023-08-01 18:33 ` Eric Sunshine
2023-08-01 20:50 ` Taylor Blau
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=3267d00f-d7b7-1288-108c-21823265d854@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).