Re: PATCH: improve git switch documentation

From: Sergey Organov <sorganov@gmail.com>
Date: Jul 13, 2021, 10:57 UTC
Message-ID: <87y2aalbvq.fsf@osv.gnss.ru>
In-Reply-To: <60ec715c8338_a452520896@natae.notmuch>

Felipe Contreras <felipe.contreras@gmail.com> writes:

Show 27 quoted lines

> Sergey Organov wrote:
>> Felipe Contreras <felipe.contreras@gmail.com> writes:
>> 
>> > Sergey Organov wrote:
>> 
>> [...]
>> 
>> >> Creating (a branch) is fundamentally different operation than switching
>> >> to (a branch), and that's why the former doesn't fit into "git switch".
>> >
>> > Not in my mind. Instead of switching to an existing branch, I'm switching
>> > to a new branch, which is easily understood by
>> > `git switch --new branch`.
>> 
>> To me:
>> 
>> "create a new branch" is basic operation.
>> 
>> "switch to another branch" is basic operation.
>> 
>> "create a new branch and then switch to it" is compound operation.
>
> Compound operations soon become basic operations in the mind of an
> expert.
>
> Lifting your feet, and then landing your feet might be basic operations
> when you are 1 yo, but soon enough they become "walking".

[caveat: please don't take the rest of this post too seriously]

Yeah, using another name for a compound is yet another option indeed. "git cretching"?

>
> Similarly checking out a commit and then cherry-picking a sequence of
> commits while resolving conflicts becomes "rebasing".

This is very questionable example. Please don't let me even start on this.

Show 7 quoted lines

>
> In my mind I'm not doing two operations, it's one operation with a
> modifier:
>
>   git switch --new branch
>
> --new is an adverb, not an operation.

Well, let's see:

    git walk "First Avenue"
    git walk parkway

then, suddenly:

    git walk --new road

Just an adverb, a modifier. As if no any additional operations were actually needed. Minecraft: who cares? Just saying.

Thanks,

-- 
Sergey Organov