Re: GIT vs Other: Need argument

From: Marcin Kasperski <marcin.kasperski@softax.com.pl>
Date: Apr 19, 2007, 17:49 UTC
Message-ID: <4627ABBB.8060709@softax.com.pl>
In-Reply-To: <alpine.LFD.0.98.0704190940330.9964@woody.linux-foundation.org>

Show 5 quoted lines

>> I guess that we should not say that Git is complicated. People tend to 
>> believe that, but it is simply not true. (...)
>
> I agree. And to some degree I suspect that the documentation pushes some 
> of the advanced things a bit *too* eagerly. (...)

As I am among those, who think that git *is* complicated, I decided to sit down, and find out why exactly I think so. Here are the top words/options/concepts, which I faced almost immediately while trying GIT, and which I find confusing:

rebase index revtree reset ref / refs rev-list rev-parse

At the same time, concepts like add, rm, commit, push, pull, merge are natural and easily understandable.

$ 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.