> On Mon, Apr 17, 2023 at 1:19 AM Uwe Brauer <o...@mat.ucm.es> wrote:

> Those are *suggestions* of what you should run. It doesn't do
> anything, and obviously you shouldn't do `git switch HEAD`.

> The error message is pretty much telling you what to do:

>   git push hg-remote remotes/origin/modernize:refs/heads/modernize

> Why didn't you try that?

 I did, but the commits where pushed as bookmarks not as named-branches

I thought 
git config remote.hg-remote.push 'refs/heads/*:refs/heads/branches/*'

Would have the effect that I don't need to run 

git push hg-remote  

Or whatever it is.

I am deeply confused. 

I understood the first (cumbersome) method

    1. Set up remote: git remote add hg-remote 

    2. Checkout each remote branch

    3. Run, for example git push default:/branches/default

So I thought running 
git config remote.hg-remote.push 'refs/heads/*:refs/heads/branches/*'

Would shorten 
the command 

git push default:/branches/default


git push default

Now it gets even more absurd 

I run 

git push hg-remote default

Everything fine. A named branch default is generated.

I run 

git push hg-remote remotes/origin/strings:refs/heads/strings 

Then a named branch documentation is generated and a bookmark «strings»

Why that?
I don't know what to say.

If I checkout each branch and push them then everything seems find but
suppose I had 100 branches, I need to checkout each, well....

> But you can clone it once, set up all the branches once, push all the
> branches ini order once, and forget about that step.

> After that you can just pull from one repo and push to another.

Warning: Content may be disturbing to some audiences
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine. 

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to