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

2023-04-18 Thread Uwe Brauer
>>> "FC" == Felipe Contreras writes: > On Tue, Apr 18, 2023 at 1:03 AM Uwe Brauer wrote: >> >> > 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

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

2023-04-18 Thread Felipe Contreras
On Tue, Apr 18, 2023 at 1:03 AM Uwe Brauer wrote: > > > 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 It does here. (

[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] Re: [and remote branch tracking]

2023-04-16 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 Ah, right. I

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

2023-04-16 Thread Felipe Contreras
On Sun, Apr 16, 2023 at 2:31 PM Uwe Brauer wrote: > > > On Sun, Apr 16, 2023 at 3:01 AM Uwe Brauer wrote: > > > git-remote-hg, and I wouldn't call it a "plugin", git doesn't have > > plugins. It's just a tool. > > > > I'm not sure what's going on here, as I don't have the code of > > `mygit-push-

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

2023-04-16 Thread Uwe Brauer
> On Sun, Apr 16, 2023 at 3:01 AM Uwe Brauer wrote: > git-remote-hg, and I wouldn't call it a "plugin", git doesn't have > plugins. It's just a tool. > I'm not sure what's going on here, as I don't have the code of > `mygit-push-named-branch`, but I suspect it's doing something like: > git

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

2023-04-16 Thread Felipe Contreras
On Sun, Apr 16, 2023 at 6:15 AM Uwe Brauer wrote: > > >>> "FC" == Felipe Contreras writes: > > > On Sun, Apr 16, 2023 at 3:01 AM Uwe Brauer wrote: > >> > >> > git for-each-ref --format='git switch %(refname:lstrip=3)' > >> > refs/remotes/origin > >> > > > git-remote-hg, and I wouldn't call i

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

2023-04-16 Thread Uwe Brauer
>>> "FC" == Felipe Contreras writes: > On Sun, Apr 16, 2023 at 3:01 AM Uwe Brauer wrote: >> >> > git for-each-ref --format='git switch %(refname:lstrip=3)' >> > refs/remotes/origin >> > git-remote-hg, and I wouldn't call it a "plugin", git doesn't have > plugins. It's just a tool. Ok.

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

2023-04-16 Thread Felipe Contreras
On Sun, Apr 16, 2023 at 3:01 AM Uwe Brauer wrote: > > > git for-each-ref --format='git switch %(refname:lstrip=3)' > > refs/remotes/origin > > Changing slightly the topic, when I am using your git-hg-remote plugin git-remote-hg, and I wouldn't call it a "plugin", git doesn't have plugins. It'

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

2023-04-16 Thread Uwe Brauer
> git for-each-ref --format='git switch %(refname:lstrip=3)' > refs/remotes/origin Changing slightly the topic, when I am using your git-hg-remote plugin I need to do a lot of pushes from git branch to mercurial named-branches like git remote add hg-remote hg::../mercurial-matlab-emacs-de

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

2023-04-16 Thread Uwe Brauer
> On Sat, Apr 15, 2023 at 2:35 AM Uwe Brauer wrote: > Not all references are branches, but all the ones that are branches > are fetched, except in a different namespace: /refs/remotes. > Local branches are /refs/heads, and that's what `git branch` shows. > Remote branches are in /refs/remotes,