git/list[1] front-page[2] threads[3] people[4] search[5] about
 

RE: Bug report

From
rsbecker@nexbridge.com <rsbecker@nexbridge.com>
Date
Jul 19, 2024, 20:40 UTC
Message-ID
<019001dada1b$f5a822e0$e0f868a0$@nexbridge.com>
In-Reply-To
<ZprI_wP1km8eA7HA@tapette.crustytoothpaste.net>
On Friday, July 19, 2024 4:14 PM, brian m. carlson wrote:
Show 29 quoted lines
>On 2024-07-19 at 18:34:29, Roman Dvoskin wrote:
>> Thank you for filling out a Git bug report!
>> Please answer the following questions to help us understand your issue.
>>
>> What did you do before the bug happened? (Steps to reproduce your
>> issue) I renamed an existing branch to a new name What did you expect
>> to happen? (Expected behavior) When I git push I expected the new name
>> to be used to match the remote branch What happened instead? (Actual
>> behavior) I was prompted to use git push HEAD:<old_branch_name> What's
>> different between what you expected and what actually happened?
>> I expected for the new branch name to be used, as if it was always the
>> branch name Anything else you want to add:
>
>I'm not sure I understand exactly the message that you saw here, and I suspect if I
>don't understand, it's possible other people on the list don't either. Could you copy
>and paste the exact output you saw here so that we can see what the prompt looks
>like and the exact response you saw? That would help us understand whether the
>behaviour you saw is a bug or not, or if perhaps maybe the documentation is
>unclear.
>
>Also, to be sure I understand, you did something like this:
>
>----
>git branch -m foo bar
>git push origin bar
>----
>
>and you expected the local branch `bar` to be pushed to the remote branch `bar`,
>correct?

Would not the logical way to do this be: git switch -c foo # Or however the branch is set up. git push --set-upstream origin bar # Sets the association to the remote branch

I could not get the original attachment (filtered out).
Previous: Roman Dvoskin
Message 4 of 4 in “Bug report”
  1. Roman DvoskinJul 19, 2024
  2. brian m. carlsonJul 19, 2024
  3. Roman DvoskinJul 19, 2024
  4. rsbecker@nexbridge.comJul 19, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.