> On 7. Nov 2022, at 19:58, Yuri <[email protected]> wrote: > > This happened several times to me. I had to revert commits. Now this > happened again. > > > When several ports have changes in the tree and one of the ports is committed > with 'cd <categ>/<name> && git commit .' - other ports sometimes also get > into the commit. > > In the message git shows correct files under 'Changes to be committed:' and > 'Changes not staged for commit:'. > > But the commit actually contains files "not staged for commit". > > > I wonder if anyone else experienced this problem. > Are you using any commit hooks? -m > > > Yuri > > >
