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

From: Jakub Narebski <jnareb@gmail.com>
Date: Dec 6, 2006, 12:32 UTC
Message-ID: <el6d50$p7e$2@sea.gmane.org>
In-Reply-To: <Pine.LNX.4.63.0612061325320.28348@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin wrote:

Show 5 quoted lines

> +  * Since every working tree contains a repository, a commit will not
> +    publish your changes; it will only create a revision. You have to
> +    "push" your changes to a public repository to make them visible
> +    to others.
> +

I'm not sure about context of this addition, but it is simply not true if you publish your working repository. Granted, usually one sets up bare public publishing repository...

By publish I mean set up http(s):// or git://, or ssh+git://, or local transport.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

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