From: Baruch Burstein <bmburstein@gmail.com>
To: git@vger.kernel.org
Subject: misleading message printed when worktree add fails
Date: Sun, 28 Nov 2021 08:50:54 +0200 [thread overview]
Message-ID: <CA+34VNLj6VB1kCkA=MfM7TZR+6HgqNi5-UaziAoCXacSVkch4A@mail.gmail.com> (raw)
Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue)
run `git worktree add <path> <branch>`, where <branch> is an already
checked-out branch
What did you expect to happen? (Expected behavior)
fail to create worktree
What happened instead? (Actual behavior)
worktree was not created, but a confusing message was printed:
"Preparing worktree (checking out '<branch>')"
What's different between what you expected and what actually happened?
The printed message seems to indicate that the command was a success,
when in fact
it was not
Anything else you want to add:
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.33.1.windows.1
cpu: x86_64
built from commit: 05d80adb775077d673fab685009ede4a1003ed92
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Windows 10.0 18363
compiler info: gnuc: 10.3
libc info: no libc information available
$SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe
next reply other threads:[~2021-11-28 6:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 6:50 Baruch Burstein [this message]
2021-11-28 12:37 ` misleading message printed when worktree add fails Eric Sunshine
2021-11-28 16:47 ` Baruch Burstein
2021-11-28 17:00 ` Eric Sunshine
2021-11-28 17:11 ` rsbecker
2021-11-30 4:46 ` Eric Sunshine
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='CA+34VNLj6VB1kCkA=MfM7TZR+6HgqNi5-UaziAoCXacSVkch4A@mail.gmail.com' \
--to=bmburstein@gmail.com \
--cc=git@vger.kernel.org \
/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).