Re: PATCH: improve git switch documentation

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Jul 12, 2021, 16:58 UTC
Message-ID: <60ec74c513b2b_a45252081b@natae.notmuch>
In-Reply-To: <54644739-2138-8086-1696-d3c52960216c@mfriebe.de>

Martin wrote:

Show 20 quoted lines

> On 12/07/2021 18:28, Felipe Contreras wrote:
> > Martin wrote:
> >> On 11/07/2021 01:35, Felipe Contreras wrote:
> > 
> >>> Do this:
> >>>
> >>>     -N <branch>::
> >>>       Create a new branch like '--new', but if it already exists reset it
> >>>       like '--reset'.
> > 
> >> Or even shorter
> >>         See the --new option.
> >>         Allows to re-use a branch-name and may drop commits
> >>         [resetting it].
> > 
> > Yes, it is shorter, but now it doesn't even say what it does.
> > 
> 
> Ok instead of " see the --new option"
> use "Same as the --new option, but allows...."

Yeah, that explains more, but what happend when you use a branch name that already exists? Still not explained.

-- 
Felipe Contreras

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