Git development
 help / color / mirror / Atom feed
From: Michael Montalbo <mmontalbo@gmail.com>
To: shrimech <eddinen77@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] interactive: add interactive command helper
Date: Sun, 2 Aug 2026 07:46:04 -0700	[thread overview]
Message-ID: <am9Vy9vMsixhaR9E@nixos> (raw)
In-Reply-To: <20260802032549.50389-1-eddinen77@gmail.com>

On Sat, Aug 01, 2026 at 11:25:48PM -0400, shrimech wrote:
> Git does not provide a simple interactive entry point for common working-tree and history operations.
> 
> Add a new git interactive command that presents a terminal menu for common operations, including status, adding changed files, log, graph output, branch listing, and help.
> 

Git comes with built-in GUI tools in git-gui and gitk. Also there are
several third-party frontends[1] available for Git. Why add another
built-in interactive interface instead of modify or adding to what
already exists?

[1] https://git-scm.com/tools/guis

> diff --git a/git-interactive b/git-interactive
> new file mode 100755
> index 0000000000000000000000000000000000000000..980a21c967d02ab121a54ee586cc9de4a98aa725
> GIT binary patch
>

I think including this binary patch was a mistake?


  reply	other threads:[~2026-08-02 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-02  3:25 [PATCH] interactive: add interactive command helper shrimech
2026-08-02 14:46 ` Michael Montalbo [this message]
     [not found]   ` <CAHiURhuC-dnUJ80T7f3ZynV_qj-b9_9Rs0YxyibCNDeNnuKEJA@mail.gmail.com>
2026-08-02 22:52     ` Michael Montalbo
2026-08-04  8:35   ` Kristoffer Haugsbakk

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=am9Vy9vMsixhaR9E@nixos \
    --to=mmontalbo@gmail.com \
    --cc=eddinen77@gmail.com \
    --cc=git@vger.kernel.org \
    /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