Re: Cleaning up git user-interface warts

From: Nicolas Pitre <nico@cam.org>
Date: Nov 15, 2006, 04:46 UTC
Message-ID: <Pine.LNX.4.64.0611142342160.2591@xanadu.home>
In-Reply-To: <7vd57ps51c.fsf@assigned-by-dhcp.cox.net>

On Tue, 14 Nov 2006, Junio C Hamano wrote:

Show 5 quoted lines

> Yes.  The current "merge" started its life as Linus's porcelain
> (we did not have fetch and pull infrastructure back then) but
> quickly has become just a helper for pull to produce a merge
> commit.  If anybody thinks its UI is good as a general end-user
> level command, there is a need for "head examination".

If you mean "git merge" it sure needs to be brought forward. It can't be clearer than:

	git-merge the_other_branch

or

	git-merge git://repo.com/time_machine.git

to instantaneously understand what is going on.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.