From: Kevin Daudt <me@ikke.info>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: "Konstantin Khomoutov" <kostix+git@007spb.ru>,
git@vger.kernel.org,
"Santiago Perez De Rosso" <sperezde@csail.mit.edu>,
"Daniel Jackson" <dnj@csail.mit.edu>,
"Greg Wilson" <gvwilson@third-bit.com>,
"Jakub Narębski" <jnareb@mat.umk.pl>
Subject: Re: "Purposes, Concepts,Misfits, and a Redesign of Git" (a research paper)
Date: Sat, 1 Oct 2016 22:13:25 +0200 [thread overview]
Message-ID: <20161001201325.GA29588@ikke.info> (raw)
In-Reply-To: <481910fd-5a5f-ffc6-b98c-61d48b4a2e49@gmail.com>
On Sat, Oct 01, 2016 at 12:24:57AM +0200, Jakub Narębski wrote:
>
> | 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.
next prev parent reply other threads:[~2016-10-01 20:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 16:14 "Purposes, Concepts,Misfits, and a Redesign of Git" (a research paper) Konstantin Khomoutov
2016-09-30 22:24 ` Jakub Narębski
2016-10-01 20:13 ` Kevin Daudt [this message]
2016-10-01 21:39 ` Jakub Narębski
[not found] ` <CAKbZu+BUOAjixTmEC4octseyJbMnFuaCTtLT9hx3H10=AECeKw@mail.gmail.com>
2016-10-05 10:14 ` Jakub Narębski
2016-10-05 10:42 ` Duy Nguyen
[not found] ` <CAKbZu+CTobJ9omSDtK5WQxUZuq=b0g0r59k+9MFFy247YijgUw@mail.gmail.com>
2016-10-07 18:05 ` Jakub Narębski
2016-10-07 17:52 ` Konstantin Khomoutov
2016-10-07 18:56 ` Jakub Narębski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161001201325.GA29588@ikke.info \
--to=me@ikke.info \
--cc=dnj@csail.mit.edu \
--cc=git@vger.kernel.org \
--cc=gvwilson@third-bit.com \
--cc=jnareb@gmail.com \
--cc=jnareb@mat.umk.pl \
--cc=kostix+git@007spb.ru \
--cc=sperezde@csail.mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).