RE: What's in git.git (stable)

From: Raimund Bauer <ray@softwarelandschaft.com>
Date: Dec 15, 2006, 09:55 UTC
Message-ID: <002401c7202f$34f2af20$0b0aa8c0@abf.local>
In-Reply-To: <200612150858.25988.andyparkins@gmail.com>

Show 11 quoted lines

> Yep.  Although you've persuaded me with the above example, I 
> think this is the 
> correct path.  It's not wise to add every bell and whistle 
> just because we 
> can.  As long as there is /a/ way to achieve every task, 
> that's good enough, 
> we don't need every way to achieve every task.  We might even 
> argue that 
> git's flexibility is what makes it harder to learn.  It's 
> similar to UNIX in 
> that respect - hard to learn, easy to use.

So we prefer to tell users "You can do what you want with these 3 commands, since we don't want to confuse use with another option to do it with just 1"?

> Andy

-- 
best regards

  Ray

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