← Back to context

Comment by kazinator

9 hours ago

"git gui" is not just a wrapper for commands; it has usefully different workflows.

For instance, you can visually select a range of lines in a file, and stage those lines.

This is much easier than doing "git add --patch" and using edit, where you are deleting unwanted lines starting with +, turning - lines into context and whatnot.

I have found it useful to fire up "git gui" during rebase workflows with conflicts. It helps with the "git add" commands you would have to do to add conflict-resolved files into the patch and whatnot.

> For instance, you can visually select a range of lines in a file, and stage those lines.

Isn't this the standard for every Git GUI? Are there people who use a GUI that can't do that?

  • No idea; I don't know every git gui; I'm talking about that Tcl/Tk thing that is literally run with "git gui".

    It would be pretty pointless to go out of the way to use something that doesn't come from the git project, yet is less capable (unless it had some overriding killer feature for the sole sake of which it was invoked).