Date: Tue, 8 Nov 2022 00:55:50 +0100 From: Michael Gmelin <grembo@freebsd.org> To: Yuri <yuri@freebsd.org> Cc: ports@freebsd.org Subject: Re: Git malfunctions on the ports tree Message-ID: <A82AA268-916A-45E5-ABC0-2BDDB4FDA250@freebsd.org> In-Reply-To: <97f8239e-86d5-d3c6-8e66-2174d83ae1db@tsoft.com> References: <97f8239e-86d5-d3c6-8e66-2174d83ae1db@tsoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 7. Nov 2022, at 19:58, Yuri <yuri@freebsd.org> wrote: >=20 > =EF=BB=BFThis happened several times to me. I had to revert commits. Now t= his happened again. >=20 >=20 > When several ports have changes in the tree and one of the ports is commit= ted with 'cd <categ>/<name> && git commit .' - other ports sometimes also ge= t into the commit. >=20 > In the message git shows correct files under 'Changes to be committed:' an= d 'Changes not staged for commit:'. >=20 > But the commit actually contains files "not staged for commit". >=20 >=20 > I wonder if anyone else experienced this problem. >=20 Are you using any commit hooks? -m >=20 >=20 > Yuri >=20 >=20 >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A82AA268-916A-45E5-ABC0-2BDDB4FDA250>