GNU bug report logs - #75655
configure doesn't update Makefile

Previous Next

Full log

View this message in rfc822 format

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>, Pip Cet <pipcet <at> protonmail.com>
Cc: schwab <at> linux-m68k.org, 75655 <at> debbugs.gnu.org
Subject: bug#75655: configure doesn't update Makefile
Date: Thu, 23 Jan 2025 12:13:15 -0600

Eli Zaretskii <eliz <at> gnu.org> writes:

> You should not have uncommitted changes, ever.  Always either commit
> them (on a local branch if needed) or stash them.  Keeping uncommitted
> changes runs the risk of pushing them inadvertently with unrelated
> changes (it happened to me and to others).

FWIW, while you're probably right in the abstract, I have a habit of
doing exactly that.  This is for various reasons: it's impractical to
commit them only to a specific branch, stashing gets old quick, and it's
also quite inconvenient to keep them outside the repository.  Right now,
for instance, I have nine important yet untracked files in my
repository.

I can't remember that I have ever committed any unrelated files by
accident.  It seems hard to make that mistake in Magit, but what do I
know.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.