From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.7 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by dcvr.yhbt.net (Postfix) with ESMTP id 13E911F910 for ; Wed, 2 Nov 2022 15:46:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229553AbiKBPpr (ORCPT ); Wed, 2 Nov 2022 11:45:47 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57180 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229485AbiKBPpq (ORCPT ); Wed, 2 Nov 2022 11:45:46 -0400 Received: from mail-yw1-f169.google.com (mail-yw1-f169.google.com [209.85.128.169]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7367729346 for ; Wed, 2 Nov 2022 08:45:05 -0700 (PDT) Received: by mail-yw1-f169.google.com with SMTP id 00721157ae682-369426664f9so169561037b3.12 for ; Wed, 02 Nov 2022 08:45:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=lwrqINt+o3VBNJ0MXhIVUnE2Lm24zgUZdqAgbUTnD3I=; b=trE8eyijZavBFdrvKzRSNhaurEelmE8wfFja+FiA6GvzNSuhXgUO1Tcd2gUaktTS5q QjdsyaTu/oSFRA3QyOEEtnFE4cTbLsOo1ihLNEHOmHirIotD3AQ1/s+TbW4XHdx3mT9R YlXVxiGgZib99Sbp8dMvVThOw9lGS/EA7gO4b8xR82jD2SL/VJ/hPLfzk6ZNxCTNrsQU fMZMLEpagkn7e3LUdeyrDtYm8usx9haE/2flLKMyPWVzxiTj9Oa2T6K/GD2YaGlPeXKO H+bJ5lCcA/i5iL9KqPtO61tRszAuZDCFg8XRiggOhRoyQtDmOWPQfClQfNgvuT+Th035 GuvA== X-Gm-Message-State: ACrzQf3W9brKp1OfmbefBG34j4lZawjgMfloHwpzs9dHApvDxwI0tfDx 70chBzYNNQtiF4f5ScDLDTehrmhpH1m1vqccLnz0GXOkNMQ= X-Google-Smtp-Source: AMsMyM5Jy7BaSS0N18hu+Et3WGVdE3OxLMT/mSYviQktJILBrczamqEWgJ1PtxdG1O0OzS5g+RH4LkvTbB5uFv2pebM= X-Received: by 2002:a81:4fcf:0:b0:36f:cd8d:fefd with SMTP id d198-20020a814fcf000000b0036fcd8dfefdmr23523097ywb.199.1667403904497; Wed, 02 Nov 2022 08:45:04 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Junio C Hamano Date: Wed, 2 Nov 2022 08:44:53 -0700 Message-ID: Subject: Re: [PATCH v2] Mention that password could be a personal access token. To: Eric Sunshine Cc: M Hickford via GitGitGadget , git@vger.kernel.org, Jeff King , =?UTF-8?B?w4Z2YXIgQXJuZmrDtnLDsCBCamFybWFzb24=?= , M Hickford Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Wed, Nov 2, 2022 at 3:55 AM Eric Sunshine 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"?