From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
"SZEDER Gábor" <szeder.dev@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>
Subject: [PATCH 0/1] bundle verify: improve the user experience when called without a .git/ directory
Date: Mon, 27 May 2019 12:59:13 -0700 (PDT) [thread overview]
Message-ID: <pull.226.git.gitgitgadget@gmail.com> (raw)
The git bundle verify <bundle> command really needs access to a .git/
directory. But it did not make sure, instead erroring out with a BUG(),
making for a terrible user experience.
This patch fixes that.
Johannes Schindelin (1):
bundle verify: error out if called without an object database
bundle.c | 3 +++
t/t5607-clone-bundle.sh | 6 ++++++
2 files changed, 9 insertions(+)
base-commit: 8104ec994ea3849a968b4667d072fedd1e688642
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-226%2Fdscho%2Ffix-bundle-verify-segfault-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-226/dscho/fix-bundle-verify-segfault-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/226
--
gitgitgadget
next reply other threads:[~2019-05-27 19:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 19:59 Johannes Schindelin via GitGitGadget [this message]
2019-05-27 19:59 ` [PATCH 1/1] bundle verify: error out if called without an object database Johannes Schindelin via GitGitGadget
2019-05-27 20:08 ` brian m. carlson
2019-05-27 20:20 ` Johannes Schindelin
2019-05-28 1:51 ` Jeff King
2019-05-28 11:17 ` Johannes Schindelin
2019-05-28 20:58 ` Jeff King
2019-05-28 20:03 ` Junio C Hamano
2019-05-28 21:04 ` Jeff King
2019-05-28 21:09 ` Junio C Hamano
[not found] ` <pull.226.v2.git.gitgitgadget@gmail.com>
[not found] ` <8467593c158ffac56897cf02e165173d9c0b5880.1558988458.git.gitgitgadget@gmail.com>
2019-05-27 20:25 ` [PATCH v2 " brian m. carlson
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=pull.226.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=konstantin@linuxfoundation.org \
--cc=szeder.dev@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.