From nobody Mon Nov 7 23:55:50 2022 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4N5p5r4913z4glm8 for ; Mon, 7 Nov 2022 23:56:00 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.evolve.de (mail.evolve.de [213.239.217.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail.evolve.de", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4N5p5p6x4tz5ZD8; Mon, 7 Nov 2022 23:55:58 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: by mail.evolve.de (OpenSMTPD) with ESMTP id 68ac61ff; Mon, 7 Nov 2022 23:55:51 +0000 (UTC) Received: by mail.evolve.de (OpenSMTPD) with ESMTPSA id 0ac4bbe6 (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Mon, 7 Nov 2022 23:55:51 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org Mime-Version: 1.0 (1.0) Subject: Re: Git malfunctions on the ports tree From: Michael Gmelin In-Reply-To: <97f8239e-86d5-d3c6-8e66-2174d83ae1db@tsoft.com> Date: Tue, 8 Nov 2022 00:55:50 +0100 Cc: ports@freebsd.org Message-Id: References: <97f8239e-86d5-d3c6-8e66-2174d83ae1db@tsoft.com> To: Yuri X-Mailer: iPhone Mail (20B82) X-Rspamd-Queue-Id: 4N5p5p6x4tz5ZD8 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=softfail (mx1.freebsd.org: 213.239.217.29 is neither permitted nor denied by domain of grembo@freebsd.org) smtp.mailfrom=grembo@freebsd.org X-Spamd-Result: default: False [-2.60 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:24940, ipnet:213.239.192.0/18, country:DE]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[ports@freebsd.org]; ARC_NA(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all:c]; RCVD_TLS_LAST(0.00)[]; FREEFALL_USER(0.00)[grembo]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[freebsd.org]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N > On 7. Nov 2022, at 19:58, Yuri 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 / && 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