Re: [PATCH v2] Mention that password could be a personal access token.

From: Philip Oakley <philipoakley@iee.email>
Date: Nov 2, 2022, 17:30 UTC
Message-ID: <83d3c28b-9b33-fa17-c0ca-85e790e52dad@iee.email>
In-Reply-To: <CAPig+cRy66HNfTnNQC4PcAaMR-m-DwUbdETsy0zBX4saG7F4Ng@mail.gmail.com>

On 02/11/2022 15:51, Eric Sunshine wrote:

Show 13 quoted lines

> On Wed, Nov 2, 2022 at 11:45 AM Junio C Hamano <gitster@pobox.com> wrote:
>> On Wed, Nov 2, 2022 at 3:55 AM Eric Sunshine <sunshine@sunshineco.com> wrote:
>>> How about a different approach, calling it a "secret" first, and then
>>> defining "secret" as different names for "password".
>> Or more directly, say "password" and parenthetically add that some hosting
>> sites may call it with different names like "personal tokens"?
> I tried the parenthetical approach first but the sentence structure
> became too complex and more difficult to understand. Having a separate
> sentence helped simplify. That said, perhap something like this?
>
>     Git will sometimes need credentials from the user in order to
>     perform operations; for example, it may need to ask for a username
>     and password in order to access a remote repository over HTTP.  In

Perhaps s/password/secret 'password'/ here 9above0, and then talk about the names for that "secret" in the follow up sentence below.

>     place of a password, some sites may instead provide a passcode,
>     personal access token, OAuth access token, etc.  This manual...

-- Philip