How do you deal with incomplete commits?

[Thomas Friedrichsmeier]

Hi,

thanks for your answer (also to Nate). But to clarify, my question is
really: How do I _force_ myself to clean up in time?

Am Sat, 31 Oct 2020 15:44:35 +0100
schrieb Thomas Baumgart <thb at net-bembel.de>:

> On Samstag, 31. Oktober 2020 13:39:04 CET Thomas Friedrichsmeier
> wrote:

[...]

> > Say I'm working on a feature in branch A. I have some changes in my
> > working copy that are so half-baked that I don't want them to end
> > up in the commit history as such, but I don't want to throw them
> > away, either.  
> 
> I assume, you don't thing about pushing those at all.

Right, I do not intend to push those, but I'm afraid, I might (esp. in
case I'm returning to my work days, weeks or even months, later). So
I'm looking for a way to stop myself from doing so.

Thomas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: Digitale Signatur von OpenPGP
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20201031/4304e1c4/attachment.sig>