[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: How do you deal with incomplete commits?
From:       Thomas Baumgart <thb () net-bembel ! de>
Date:       2020-10-31 15:38:09
Message-ID: 4569965.sk00qvhrl2 () thb-nb
[Download RAW message or body]


Hi,

On Samstag, 31. Oktober 2020 16:24:51 CET Thomas Friedrichsmeier wrote:

> 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?

Reading your question over and over, I don't see where git is mentioned :)
This leads to a short answer: self-discipline.

My impression is that you look for a some magic feature in git that forces
you to clean up in time. Not sure if something like that exists.

> Am Sat, 31 Oct 2020 15:44:35 +0100
> schrieb Thomas Baumgart <thb@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.

-- 

Regards

Thomas Baumgart

https://www.signal.org/       Signal, the better WhatsApp
-------------------------------------------------------------
My friend couldn't afford to pay his water bill. So I sent him a 'get well soon' card.
-------------------------------------------------------------

["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]