From: Sheik <sahibzone@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Repository cloned using SSH does not respect bare repository initial branch
Date: Tue, 31 Oct 2023 02:24:46 +1100 [thread overview]
Message-ID: <b310e254-f6d3-4715-b042-341bf5a98bbc@gmail.com> (raw)
In-Reply-To: <20231030093605.GE84866@coredump.intra.peff.net>
Server version is same as client (v2.42.0) as I ran these commands all
on the same machine.
Test on ssh server:
$ git -v --build-options
#Output
git version 2.42.0
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
Thanks
Sheik
On 30/10/23 20:36, Jeff King wrote:
> On Thu, Oct 26, 2023 at 07:36:36AM +1100, Sheik wrote:
>
>> Repository cloned using SSH does not use the branch configured in the bare
>> repository however repository cloned using filesystem does as expected.
>> Shouldn't they both behave the same?
> What version of Git is running on the ssh server?
>
> Your example seems to show that the parent repository has an unborn
> branch (i.e., HEAD points to "refs/heads/test", but there are no commits
> yet). I think the server-side bits you need for that to work showed up
> in 59e1205d16 (ls-refs: report unborn targets of symrefs, 2021-02-05),
> which is in v2.31.
>
> So even though your client seems to be v2.42 (from the output you gave),
> if the server is older it may not be sending sufficient information.
> There were also some other fixes on top of that, but I _think_ they were
> all client-side (so your v2.42 clone command should be doing the right
> thing).
>
> -Peff
next prev parent reply other threads:[~2023-10-30 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 20:36 Repository cloned using SSH does not respect bare repository initial branch Sheik
2023-10-30 9:36 ` Jeff King
2023-10-30 15:24 ` Sheik [this message]
2023-10-30 17:43 ` Jeff King
2023-10-30 23:30 ` Sheik
2023-10-31 2:38 ` Sheik
2023-10-30 15:33 ` Sheik
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=b310e254-f6d3-4715-b042-341bf5a98bbc@gmail.com \
--to=sahibzone@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).