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=0.1 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE 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 8BD601F953 for ; Thu, 10 Feb 2022 19:17:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1343871AbiBJTRr (ORCPT ); Thu, 10 Feb 2022 14:17:47 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:52546 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1343860AbiBJTRp (ORCPT ); Thu, 10 Feb 2022 14:17:45 -0500 Received: from pb-smtp21.pobox.com (pb-smtp21.pobox.com [173.228.157.53]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EA72D9D for ; Thu, 10 Feb 2022 11:17:45 -0800 (PST) Received: from pb-smtp21.pobox.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id A0464197841; Thu, 10 Feb 2022 14:17:45 -0500 (EST) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=BCz5AUE8FdF0heYgLCptuLA64WYt4lNz85sHSa w69+A=; b=Iye+zOIOVhXlOXpXFtGHxbnB2UJVWxhyHli6wdTv/WU5nSv0nvQ0k4 u6nbNdc/GXSt2fcCyvR6GKtJvr1L8VVccYB8f+W4yOOZwWOUlTu9TBQdcVtirfJk zZy7S4rJSHWm5SgJgiXqlQoRqfxxQ5cJMgYmfuqyi0fWZK5A1Q7GE= Received: from pb-smtp21.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 972C5197840; Thu, 10 Feb 2022 14:17:45 -0500 (EST) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [35.185.212.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp21.pobox.com (Postfix) with ESMTPSA id BBE9919783F; Thu, 10 Feb 2022 14:17:41 -0500 (EST) (envelope-from junio@pobox.com) From: Junio C Hamano To: Han-Wen Nienhuys Cc: Elijah Newren , Git Mailing List , Derrick Stolee Subject: Re: [PATCH] glossary: describe "worktree" References: Date: Thu, 10 Feb 2022 11:17:40 -0800 In-Reply-To: (Han-Wen Nienhuys's message of "Thu, 10 Feb 2022 19:36:49 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: 1E37DA24-8AA6-11EC-9810-CBA7845BAAA9-77302942!pb-smtp21.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Han-Wen Nienhuys writes: >> > Is this glossary the official definition of what things are? If so, >> > the source code should refer to there. If not -except for confusion- >> > how bad is it if the info in the glossary is inaccurate? >> >> Developer and end-user confusion ensues. > > that's why I said: "except for confusion" :-) > > I'm asking to understand if there is anything stopping us from > changing the glossary to match the current code. I do not think so. It will give us a chance to rethink what we have in the code, too. It is possible that we may end up concluding that it is better to leave a "pseudoref" always as a file inside $GIT_DIR regardless of what ref backend is in use, for example.