Date: Mon, 07 Nov 2022 19:01:25 UTC
> On Nov 7, 2022, at 7:57 PM, Yuri <yuri@FreeBSD.org> 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. > > > > Yuri > > > I can recollect having something like this a couple of months ago but then I started using git add . before git commit. And the problem went away.