Re: [PATCH] branch: rework the descriptions of rename and copy operations
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 19, 2024, 19:49 UTC
- Message-ID
- <xmqq8r3g8caz.fsf@gitster.g>
- In-Reply-To
- <be91f3ad9305366c1385c2da4881537e@manjaro.org>
Dragan Simic <dsimic@manjaro.org> writes:
Show 10 quoted lines
> Regarding the branch copy and rename operations and their argument > names, perhaps the following would be a good choice: > > --copy [<branch>] <destination> > --move [<branch>] <destination> > > It would clearly reflect the nature of the performed operations, while > still using "<branch>" consistently, this time to refer to the source > branch. Using "<destination>" to select the destination name should > be pretty much self-descriptive, if you agree.
Awful. While I was skimming the messages without reading the Subject line (hence without realizing that this is about improving the existing documentation and not adding new features), I thought that these two are about moving branch to a remote repository that is named with <destination>.
My advice would be to stick to <old> vs <new> that contrasts well.
Thanks.