Git development
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Stefan Haller <lists@haller-berlin.de>
Cc: Junio C Hamano <gitster@pobox.com>,
	"D. Ben Knoble" <ben.knoble@gmail.com>,
	git@vger.kernel.org,
	Christian Couder <christian.couder@gmail.com>,
	"schacon@gmail.com" <schacon@gmail.com>
Subject: Re: Can we do better than "git checkout/add -p"
Date: Mon, 10 Aug 2026 10:45:31 +0200	[thread overview]
Message-ID: <anmPq_WN33chIEhL@pks.im> (raw)
In-Reply-To: <26c2f7e0-03ef-4c45-8175-adcc2e0395ac@haller-berlin.de>

On Mon, Aug 10, 2026 at 09:26:55AM +0200, Stefan Haller wrote:
> On 10.08.26 08:03, Patrick Steinhardt wrote:
> > I've been playing around with the thought of introducing ncurses-based
> > interfaces into Git. I've been mostly thinking about git-history(1) here
> > so that you can just move commits around, squash them together, drop
> > them and so on. But I think fancy stuff like TUIs can also be applied to
> > other parts of Git, as well, to make things a bit more visual to our
> > users and, as a consequence, easier to use.
> 
> That sounds a whole lot like lazygit to me [1]; it does all those things
> in a rather intuitive way, including Junio's original use case of
> selecting a hunk and staging or discarding it.
> 
> Is it really worth adding such functionality to core git? I like the
> idea of tools specializing on what they do well; core git on providing
> the core functionality, GUI tools on presenting it in a UI.
> 
> [1] https://github.com/jesseduffield/lazygit

I think it depends. There are lots of users out there who use core Git,
only, and we often hear complaints from this class of users that Git
makes common workflows way too complex. I certainly think that we should
up our game and try to make such common workflows easier to wield. Tools
like JJ demonstrate that there are a bunch of improvements that we can
do, and many of those aren't even that hard to implement.

So If we see that there are use cases where core Git itself is lacking
and where the consequence is a bad user experience for common workflows
then I think that we should plug that gap in core Git itself.

That being said, I don't think we should get into the business of
building a full UI, as that feels like a can of worms indeed. Adding
something like a user interface around hunk selection certainly feels
like core functionality that I think should be in scope for Git. Whether
a full history-editing user interface should be part of core Git may be
a different question though, as this is getting significantly closer to
a full UI.

Patrick

  reply	other threads:[~2026-08-10  8:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07  4:02 Can we do better than "git checkout/add -p" Junio C Hamano
2026-08-07  7:38 ` Christian Couder
2026-08-07 11:24 ` D. Ben Knoble
2026-08-07 15:50   ` Junio C Hamano
2026-08-07 20:12     ` D. Ben Knoble
2026-08-07 20:26       ` Junio C Hamano
2026-08-10  6:03     ` Patrick Steinhardt
2026-08-10  7:26       ` Stefan Haller
2026-08-10  8:45         ` Patrick Steinhardt [this message]
2026-08-10 15:23         ` Junio C Hamano
2026-08-11  5:06           ` Patrick Steinhardt

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=anmPq_WN33chIEhL@pks.im \
    --to=ps@pks.im \
    --cc=ben.knoble@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=lists@haller-berlin.de \
    --cc=schacon@gmail.com \
    /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