Re: PATCH: improve git switch documentation

From: Martin <git@mfriebe.de>
Date: Jul 11, 2021, 10:24 UTC
Message-ID: <4cb46126-c816-065f-9052-8ef392c7778b@mfriebe.de>
In-Reply-To: <87sg0lfayd.fsf@osv.gnss.ru>

On 11/07/2021 11:37, Sergey Organov wrote:

Show 11 quoted lines

> Martin <git@mfriebe.de> writes:
> I did suggest a wording in that post:
> 
> "Allows to reuse <branch-name>. Commits from the former branch may
> become unreferenced."
> 
> Another one could be:
> 
> "Allows to reuse <branch-name>. Commits from the former branch could be
> lost."
>

"lost" is perfect for me.

"could be" is a good replacement for "may". It much stronger points to "this may or may not be"

"could be"  should definitely be used.

Afaik many tech docs try to avoid "may", "can", "must not"....

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