Re: "Purposes, Concepts,Misfits, and a Redesign of Git" (a research paper)

From: Kevin Daudt <me@ikke.info>
Date: Oct 1, 2016, 20:13 UTC
Message-ID: <20161001201325.GA29588@ikke.info>
In-Reply-To: <481910fd-5a5f-ffc6-b98c-61d48b4a2e49@gmail.com>

On Sat, Oct 01, 2016 at 12:24:57AM +0200, Jakub Narębski wrote:

Show 10 quoted lines

> 
> | 7.2.1 Discussion
> [...]
> | There could be other use cases for the
> | staging area that Gitless doesn’t handle well but we expect
> | these to be fairly infrequent.
> 
> Like handling merge conflict...??? Infrequent doesn't mean
> unimportant.
>

For me the most important thing is that the lack of staging area leads on commits that have no clear goal, people just commit everything they have changed at some point, as a sort of checkpoint.

Although lots of people still do this with git currently, they don't even have the possibility[1] to improve on this.

This makes history and features like git bisect less useful.

[1] At most they can specify the files they want to commit, but this is still a very crude way to group together changes.