Re: [git-users] how is name-rev determined

On Wed, Mar 22, 2023 at 2:37 PM Uwe Brauer wrote: > > >>> "FC" == Felipe Contreras writes: > > > On Thu, Mar 16, 2023 at 3:26 PM Uwe Brauer wrote: > >> > I wrote the equivalent of hg-git for the git world: git-remote-hg [1], > >> > and there exporting named branches works fine. They have the >

Re: [git-users] how is name-rev determined

>>> "FC" == Felipe Contreras writes: > On Thu, Mar 16, 2023 at 3:26 PM Uwe Brauer wrote: >> > I wrote the equivalent of hg-git for the git world: git-remote-hg [1], >> > and there exporting named branches works fine. They have the >> > "branches/" prefix and only one head is tracked. >> >> Do

Re: [git-users] how is name-rev determined

On Thu, Mar 16, 2023 at 3:26 PM Uwe Brauer wrote: > > I wrote the equivalent of hg-git for the git world: git-remote-hg [1], > > and there exporting named branches works fine. They have the > > "branches/" prefix and only one head is tracked. > > Do you mean exporting named hg branches into git

[git-users] Git submodule update on rebase or merge

The question is why doesn't git rebase and merge have a --recurse-submodules option so that it updates the submodules when the operation is completed successfully? The submodule.recurse configuration will thus affect the rebase and merge commands so that the submodules are automatically