From: Junio C Hamano <gitster@pobox.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Ilya Kamenshchikov <ikamenshchikov@gmail.com>, git@vger.kernel.org
Subject: Re: Git branch capitalisation bug?
Date: Thu, 13 Apr 2023 13:31:13 -0700 [thread overview]
Message-ID: <xmqqfs93y166.fsf@gitster.g> (raw)
In-Reply-To: <20230413190302.drmmdrkv7vfps3qg@tb-raspi4> ("Torsten Bögershausen"'s message of "Thu, 13 Apr 2023 21:03:02 +0200")
Torsten Bögershausen <tboegi@web.de> writes:
> I am not sure, where this Capitalizations comes from.
> I don't have an account on boschdevcloud.com to test.
> Is it possible to reproduce it with a public repo ?
> Otherwise, should we suspect boschdevcloud.com for it ?
>
> Any other thoughts from anybody ?
In the transcript I do not see any "git pull" done from the other
side, so the "origin/Feature/macos_tests" in the commit decoration
that can be seen in the last part of the transcript may have been
created locally. Output from
$ git ls-remote origin | grep macos_tests
might be a way to see which end of the connection has the issue.
next prev parent reply other threads:[~2023-04-13 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 10:35 Git branch capitalisation bug? Ilya Kamenshchikov
2023-04-13 19:03 ` Torsten Bögershausen
2023-04-13 20:31 ` Junio C Hamano [this message]
2023-04-20 7:04 ` Ilya Kamenshchikov
2023-04-20 7:28 ` Chris Torek
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=xmqqfs93y166.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ikamenshchikov@gmail.com \
--cc=tboegi@web.de \
/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.