Re: seperate commits for objects already updated in index?
- From
- Paul Jakma <paul@clubi.ie>
- Date
- Mar 14, 2006, 17:27 UTC
- Message-ID
- <Pine.LNX.4.64.0603141723240.5276@sheen.jakma.org>
- In-Reply-To
- <Pine.LNX.4.64.0603140915290.3618@g5.osdl.org>
On Tue, 14 Mar 2006, Linus Torvalds wrote:
Show 5 quoted lines
> Well, I actually think git is being somewhat of an ass, for no > really good reason. It's true that you are doing something pretty > strange by _both_ using "git-update-index" and "git commit -o" but > the fact is, at least when adding files, that would be expected (ie > you have to mark a file in the index to add it).
Well, I tend to work on one thing, then notice something else unrelated (or in a support file), fix/tweak that, etc.. I use the index for 'way-point' diffs, rather than commit things I havn't quite tested yet (or dont know whether they'll be useful yet).
Show 5 quoted lines
> I also think that test is historical, from before Junio cleaned up > how "git commit" worked - it _used_ to be that "git commit" would > work in the current index, but these days it generates a new index > to commit when you do "-o", so there's really no _technical_ reason > to refuse the partial commit any more as far as I can see.
Aha. So that check possibly could just be removed?
> So I don't know. I don't think you were being dumb, I think git > could have been friendlier to you.
:)
git reset works just fine too.
regards,
-- Paul Jakma paul@clubi.ie paul@jakma.org Key ID: 64A2FF6A Fortune: A day for firm decisions!!!!! Or is it?