From: Andry <andry@inbox.ru>
To: git@vger.kernel.org
Subject: Re: Get rid of `warning: refs/remotes/origin/master usually tracks refs/heads/master, not refs/remotes/origin/master`
Date: Sun, 26 Feb 2023 00:48:08 +0300 [thread overview]
Message-ID: <1212192063.20230226004808@inbox.ru> (raw)
In-Reply-To: <942870379.20230223062101@inbox.ru>
Hello Git,
Thursday, February 23, 2023, 6:21:01 AM, you wrote:
A> Found this issue and could find a solution.
A> ...
A> Is there a way to unmirror the remote repository back?
Seems the problem was in the logic of the push algorithm.
There was 2 fors (pseudocode):
```python
for remote in remotes:
for branch in branches:
git_push([remote, ':refs/remotes/' + remote + '/' + branch])
```
Instead of 3 fors:
```python
for remote in remotes:
for ref_remote in remotes:
for branch in branches:
git_push([remote, ':refs/remotes/' + ref_remote + '/' + branch])
```
Because each remote has `num(refs) = num(branches) x num(remotes)` after the mirror.
prev parent reply other threads:[~2023-02-25 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 3:21 Get rid of `warning: refs/remotes/origin/master usually tracks refs/heads/master, not refs/remotes/origin/master` Andry
2023-02-25 21:48 ` Andry [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=1212192063.20230226004808@inbox.ru \
--to=andry@inbox.ru \
--cc=git@vger.kernel.org \
/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).