Re: [PATCH] cvs-migration document: make the need for "push" more obvious

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Dec 6, 2006, 15:16 UTC
Message-ID: <Pine.LNX.4.63.0612061613460.28348@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <20061206145802.GC1714@fieldses.org>

Hi,

On Wed, 6 Dec 2006, J. Bruce Fields wrote:

> I'd rather leave that introduction as it is--just as a section that 
> advertises the git features without trying to explain much.  And I'd 
> rather not mention push until we have a chance to explain how to use it.

You talk like you'd have an eternity to explain Git. But that is not true. A developer, especially those whom Git is forced upon, have an attention span shorter than their pub1c hair.

I _know_ that _I_ did not read the whole document about "Branching and merging in Git".

Ciao, Dscho

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