Re: What is the diff between a --soft and a blank reset

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> My reply to Chris.
>
> On Sunday, November 17th, 2024 at 02:57, Chris Torek 
> <chris.torek@gmail.com> wrote:
>
>> * With `--mixed`, `git reset` adjusts `HEAD` as before --
>> it's usually wisest to not have it adjust anything for
>> this case, in my opinion -- and then goes on to copy the
>> files from the `HEAD` commit into the index. 
>
> I didn't give any case: What are you talking about? It look's as though 
> you are pasting a custom manpage for git-reset based on keyword 
> matching. Essentially spamming the mailing list based on a keyword 
> match. Yet another manpage being written by a thirdparty when having 
> conflicting and scattered jargon makes it to where the user cannot 
> communicate in a meaningful way about using the software. You vaguely 
> show the difference (e.g. soft means job #1 and mixed means job #1 & 
> #2) however not fully answering my pinpointed question "Does this from 
> --soft: "leaves all your changed files "Changes to be committed", as  
> git status would put it.'" mean soft leaves the adds indexed but before 
> the adds were commit and without commit whereas --mixed would erase the 
> index having adds ready to commit?" conscerning what the difference 
> means in pragma. We and you need to learn English or get off of mailing 
> lists: stop spamming. I say we because you are not alone.