From: shejialuo <shejialuo@gmail.com>
To: Ronan Pigott <ronan@rjp.ie>
Cc: git@vger.kernel.org
Subject: Re: BUG: refs.c:1933: reference backend is unknown
Date: Sun, 22 Sep 2024 00:09:08 +0800 [thread overview]
Message-ID: <Zu7vpPs8fcqlMlNK@ArchLinux> (raw)
In-Reply-To: <1b9fb3f3fde62594b9ac999ffb69e6c4fb9f6fd6@rjp.ie>
On Fri, Sep 20, 2024 at 05:37:40PM +0000, Ronan Pigott wrote:
[snip]
> The following is an abort in git:
>
> $ git --version
> git version 2.46.1
> $ git --git-dir=notexist archive
> BUG: refs.c:1933: reference backend is unknown
> zsh: IOT instruction (core dumped) git --git-dir=notexist archive
>
The "git-archive(1)" command must accept at least one parameter as
"archive.c::parse_archive_args" shows:
static int parse_archive_args(...)
{
...
if (argc < 1)
usage_with_options(archive_usage, opts);
}
So, it will print the usage and exit the program. I guess you omit some
things for this bug report. Could you please give us more information to
let us dive into this?
Thanks,
Jialuo
next prev parent reply other threads:[~2024-09-21 16:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 17:37 BUG: refs.c:1933: reference backend is unknown Ronan Pigott
2024-09-21 16:09 ` shejialuo [this message]
2024-09-21 18:06 ` Ronan Pigott
2024-09-21 21:22 ` René Scharfe
2024-09-22 6:51 ` shejialuo
2024-09-22 14:41 ` shejialuo
2024-09-24 10:05 ` [PATCH 0/2] config: fix evaluating "onbranch" with nonexistent git dir Patrick Steinhardt
2024-09-24 10:05 ` [PATCH 1/2] t1305: exercise edge cases of "onbranch" includes Patrick Steinhardt
2024-09-24 16:05 ` Junio C Hamano
2024-09-24 10:05 ` [PATCH 2/2] config: fix evaluating "onbranch" with nonexistent git dir Patrick Steinhardt
2024-09-24 14:11 ` shejialuo
2024-09-24 16:17 ` Junio C Hamano
2024-09-24 14:20 ` [PATCH 0/2] " shejialuo
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=Zu7vpPs8fcqlMlNK@ArchLinux \
--to=shejialuo@gmail.com \
--cc=git@vger.kernel.org \
--cc=ronan@rjp.ie \
/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.