From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C79A2C5519F for ; Thu, 19 Nov 2020 01:51:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 4FC06246B0 for ; Thu, 19 Nov 2020 01:51:49 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=pobox.com header.i=@pobox.com header.b="lQmteQsW" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727352AbgKSBv2 (ORCPT ); Wed, 18 Nov 2020 20:51:28 -0500 Received: from pb-smtp1.pobox.com ([64.147.108.70]:58185 "EHLO pb-smtp1.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726413AbgKSBv2 (ORCPT ); Wed, 18 Nov 2020 20:51:28 -0500 Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id A3FA8A2A6D; Wed, 18 Nov 2020 20:51:25 -0500 (EST) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:message-id:mime-version:content-type; s=sasl; bh=5Iy9ucXIVPXmggLjaeTonYlbfm8=; b=lQmteQsWS+kTNrfPnO57 lzfZ1DPF+p2bb3naVKRZmO5G0mhllTmoC3gk6TZRSLGLYaQyfN/WTJ1joip29etr 7mwLkw2mJqD+cc6a9aFrdFFEoOPtG5F07qvo56fXooiuqGZWc+zDyo90WZJuZz/8 O4z42LyNpO6oq/QMFotVeNo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:message-id:mime-version:content-type; q=dns; s=sasl; b=V/Jv3aEz/urAH477LAkyuFoFmUxIcjwQRld4Zr2xPYNIT/ N3tVxjBt6jiuwmPEzdQ/e+Df3wjw2yk0C1Rzfm9lCdtLpUw5ZZqr0t6tIateNLH4 r6yHjrMNeVbBjJSq/sxSBokixOihEzIDdIKV/0MyYCNOFFO8Vb9oWqy/DNLqk= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 9C81BA2A6C; Wed, 18 Nov 2020 20:51:25 -0500 (EST) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.75.7.245]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 313C6A2A6B; Wed, 18 Nov 2020 20:51:25 -0500 (EST) (envelope-from junio@pobox.com) From: Junio C Hamano To: Philip Oakley Cc: "Eric W. Biederman" , Johannes Schindelin via GitGitGadget , git@vger.kernel.org, Johannes Schindelin Subject: Re: [PATCH 00/28] Use main as default branch name References: <87r1oraewl.fsf@x220.int.ebiederm.org> <1389dabc-33c9-1e65-a3de-43729a6c2e70@iee.email> Date: Wed, 18 Nov 2020 17:51:24 -0800 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: BB681D94-2A09-11EB-A9A7-D152C8D8090B-77302942!pb-smtp1.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Philip Oakley writes: > An alternative in the other direction is to go with the 'not currently > on any branch' (detached at nowhere) but then require users to > deliberately create their first branch with their chosen name. This > moves the 'backward incompatibility' to a different place, which may be > easier to manage. As has already been mentioned by Peff, I do not think that is a workable alternative, especially given that people are generally afraid of and easily get confused by being on a detached HEAD. And there is no such thing as unborn detached HEAD. Existing versions of Git would not consider a $GIT_DIR that does not have any HEAD, which means a new repository created by such an "initially there is no branch" version of Git cannot be accessed by any existing versions of Git. It raises the backward incompatibility of such an approach to a whole new level that is simply unmanageable, I am afraid.