Re: [PATCH 1/4] Documentation: explain push.default option a bit more

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 21, 2012, 05:42 UTC
Message-ID: <xmqqbomlzlma.fsf@junio.mtv.corp.google.com>
In-Reply-To: <4F923F3A.7050701@alum.mit.edu>

Michael Haggerty <mhagger@alum.mit.edu> writes:

Show 14 quoted lines

> only means "nuclear", I suggest that the word be avoided in this
> explanation.  Perhaps
>
>>      * `matching` - push all branches having the same name in both ends.
>>        This is for those who prepare all the branches into a publishable
>>        shape and push them out atomically, and suitable when pushing to a
>>        non-shared repository. [...]
>
> could be changed to
>
>>      * `matching` - push all branches having the same name in both ends.
>>        This allows those who prepare all the branches into a publishable
>>        shape to push them out to a non-shared repository with a single
>>        command. [...]

Sounds good.

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