From: "Björn Kautler" <Bjoern@kautler.net>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
git@vger.kernel.org, asymptosis <asymptosis@posteo.net>
Subject: Re: Bug when cloning a repository with a default branch called HEAD
Date: Mon, 31 May 2021 22:57:25 +0200 [thread overview]
Message-ID: <CAKChYSq__2dgCWVqKt1LeBs9vg8xSj2FnikDqNdgsevfz565zg@mail.gmail.com> (raw)
In-Reply-To: <CAKChYSpjOZa2F_mE_7--htzaQ1V4zWgYi8Wm4GHOiYnWoAiswA@mail.gmail.com>
Don't get me wrong, I neither want that nor intended this result.
This happened in the test suite of git-spindle which does commands
similar to what I showed as reproducer now and I just wondered what is
happening.
Imho a simple push should not be able to produce an unusable state and
I think this was not the case in the past as the tests used to work.
But this could also be caused by changes in the used fixture repo.
Am Mo., 31. Mai 2021 um 22:52 Uhr schrieb Björn Kautler <Bjoern@kautler.net>:
>
> Don't get me wrong, I neither want that nor intended this result.
> This happened in the test suite of git-spindle which does commands similar to what I showed as reproducer now and I just wondered what is happening.
>
> Imho a simple push should not be able to produce an unusable state and I think this was not the case in the past as the tests used to work. But this could also be caused by changes in the used fixture repo.
>
> Randall S. Becker <rsbecker@nexbridge.com> schrieb am Mo., 31. Mai 2021, 22:46:
>>
>> >-----Original Message-----
>> >From: <Bjoern@kautler.net>
>> On May 31, 2021 4:38 PM, Björn Kautler wrote:
>> >Subject: Re: Bug when cloning a repository with a default branch called HEAD
>> >It happens the same no matter whether on Windows or Linux.
>> >I now also have a reproduction recipe on how to get into that state.
>> >- Create the `whelk` repository with standard settings, nothing for default branch or anything is necessary
>> >- Execute this: git clone https://github.com/seveas/whelk.git
>> >whelk-src && git -C whelk-src remote add gitlab git@gitlab.com:<your
>> >namespace>/whelk.git && git -C whelk-src push gitlab
>> >refs/remotes/origin/*:refs/heads/* && git clone git@gitlab.com:git-spindle-test-vampire-1/whelk.git && git -C whelk fetch
>>
>> According to GitHub, the default branch for this repo is "main" not "HEAD". AFAIK, HEAD is a reserved ref in git and I don't think this would or should work.
>>
>> Just saying.
>> Randall
>>
prev parent reply other threads:[~2021-05-31 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 19:05 Bug when cloning a repository with a default branch called HEAD Björn Kautler
2021-05-31 4:01 ` Bagas Sanjaya
2021-05-31 4:37 ` asymptosis
[not found] ` <CAKChYSrQ3u3yH0+8Fwj-84cnAFGvuSEPHx+5Mcy8Ys4sXcN14A@mail.gmail.com>
2021-05-31 20:38 ` Fwd: " Björn Kautler
2021-05-31 20:45 ` Randall S. Becker
[not found] ` <CAKChYSpjOZa2F_mE_7--htzaQ1V4zWgYi8Wm4GHOiYnWoAiswA@mail.gmail.com>
2021-05-31 20:57 ` Björn Kautler [this message]
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=CAKChYSq__2dgCWVqKt1LeBs9vg8xSj2FnikDqNdgsevfz565zg@mail.gmail.com \
--to=bjoern@kautler.net \
--cc=asymptosis@posteo.net \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.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).