[git-users] Re: [and remote branch tracking]

2023-04-17 Thread Uwe Brauer
> On Mon, Apr 17, 2023 at 3:05 PM Uwe Brauer wrote: > git push hg-remote remotes/origin/modernize:refs/heads/branches/modernize Does not push the git branch modernize to the named branch modernize, sorry > Only if you don't specify the refspec, which is the typical way to push. You mean

[git-users] Re: [and remote branch tracking]

2023-04-17 Thread Felipe Contreras
On Mon, Apr 17, 2023 at 3:05 PM Uwe Brauer wrote: > > > On Mon, Apr 17, 2023 at 1:19 AM Uwe Brauer 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

[git-users] Re: [and remote branch tracking]

2023-04-17 Thread Uwe Brauer
> On Mon, Apr 17, 2023 at 1:19 AM Uwe Brauer 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/hea

[git-users] Re: [and remote branch tracking]

2023-04-17 Thread Felipe Contreras
On Mon, Apr 17, 2023 at 1:19 AM Uwe Brauer wrote: > > > On Sun, Apr 16, 2023 at 2:31 PM Uwe Brauer wrote: > > > You cannot push a branch you don't have. Obviously. > > > But you can create the branches without checking them out, as I > > already explained: > > > git for-each-ref --format='git s

[git-users] [step by step] (was: [and remote branch tracking])

2023-04-17 Thread Uwe Brauer
> On Sun, Apr 16, 2023 at 2:31 PM Uwe Brauer wrote: > You cannot push a branch you don't have. Obviously. > But you can create the branches without checking them out, as I > already explained: > git for-each-ref --format='git switch %(refname:lstrip=3)' > refs/remotes/origin > Or you can