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

Get rid of `warning: refs/remotes/origin/master usually tracks refs/heads/master, not refs/remotes/origin/master`

From
AAndry <andry@inbox.ru>
Date
Feb 23, 2023, 03:21 UTC
Message-ID
<942870379.20230223062101@inbox.ru>
Hello Git,
Found this issue and could find a solution.
Repro steps:
1. create a simple repo with only the master branch.
2. `git pull origin *:*` to allocate all refs (no warnings)
If try to mirror the repo into the same remote:
1. `git push origin --mirror`
Then the remote counter part falls into the mirror state and reports the warning:
1. `git pull origin *:*`

``` warning: refs/remotes/origin/master usually tracks refs/heads/master, not refs/remotes/origin/master Already up to date. ```

Tried to delete all refs in the local and remote. But didn't work. Somehow the remove remember the state.
Is there a way to unmirror the remote repository back?
Next: Andry
Message 1 of 2 in “Get rid of `warning: refs/remotes/origin/master usually tracks refs/heads/master, not refs/remotes/origin/master`”
  1. AndryFeb 23, 2023
  2. AndryFeb 25, 2023

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.