Re: seperate commits for objects already updated in index?

From: Junio C Hamano <junkio@cox.net>
Date: Mar 15, 2006, 19:25 UTC
Message-ID: <7vlkvbik8f.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <44181DFE.7080204@op5.se>

Andreas Ericsson <ae@op5.se> writes:

Show 6 quoted lines

> Can't this be done by updating .git/index first and then use the
> temporary index to commit? Then .git/index would match the current
> tree and everybody would be happy with very little tweaking. Doing the
> temporary index commit first could cause data-loss as described above
> if the updating of .git/index somehow fails and the user is unaware of
> it (or what to do to fix it).

You have to think about how to rewind it when the user decides later not to commit by for example giving an empty commit message or killing the editor. The order of things need to be to populate the index to be committed so that we can give preview in the commit log template upon 'commit -v', spawn the editor and get the final version of log, and then make a commit. So it may or may not be doable -- I haven't thought about it through, and currently have not much incentive nor inclination to think about it myself right now.