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-Status: No, score=-4.7 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A, SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 475CC1F5AE for ; Tue, 4 Aug 2020 08:51:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730020AbgHDIu7 (ORCPT ); Tue, 4 Aug 2020 04:50:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33490 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729586AbgHDIu7 (ORCPT ); Tue, 4 Aug 2020 04:50:59 -0400 Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0B598C06174A for ; Tue, 4 Aug 2020 01:50:59 -0700 (PDT) Received: by mail-pg1-x531.google.com with SMTP id s15so10185809pgc.8 for ; Tue, 04 Aug 2020 01:50:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=wouhRjdWKgYRGsCV++kmigQI0+q6ePrg54pmCNTuHYk=; b=sFoSBtWxkolsnyuKcJ8m7nr5hBnIBGI7lqYxkkHX3P2VyOyr2UyykRvCihkTXVzo4b uJKSYPsV9MCKExBSkGIJcvG7xOlMNYOCPBjhIv/sEbw75zZHGG6c2D3feaRP7RDL81u1 SgyILdxJnMU8EhhXGzofXEjAvCD3rjX66Kg8D95OipLST5V+VAd0+0o7K3Q/2G+TPXD9 YN5zGG0Fu5g3iRfr3cSOQNQJLZz90n+1OtWU+CDJyoLbImJSV0q7QA+sVAxr957iXA6l 79v1R5VKSdX1LBvLvZGVARbJxzjTgtFgPY6I0RZeNYBAVQVJSga/+kvziVmSVlqgXQag IC/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=wouhRjdWKgYRGsCV++kmigQI0+q6ePrg54pmCNTuHYk=; b=b02bj/8z1sGKDux1HTzDZzExif8MJB9/V2qXXb1DsdGAxlOxVpbEvviPxyMwPfUepy brFoMa7Kv5PegYiKd75oGQeT1hXLIztnqz+DS5HPpdfkMiPqIuFOhGqeD5FinaSFWZxS 3W3J3P4GFPURbcXPVOnZ9dauJDEC+DzssDu1098oBQphgQ0aeDOISypr/EQhuQrdJHQN WA5Ctzqtfz/3exxZ4XOCYwSSJp39v9SB05Rdk3w2MOkO1aYJZ1JGHh8HfDkDQL9zY7Uz uufmLaWjruzXg2Bf2wfAWHGu7myzog7BTr59xqV56QyKykZs3B2Bwjih3LYi3VzV9ayN Agpw== X-Gm-Message-State: AOAM530N+MXU45bIOVtzMYCc6bhZRHdd5lCmhufPNMRKMs6GH5wkDyFj fwSxYbVhPeLxow6NWXuzIhaqL2sm X-Google-Smtp-Source: ABdhPJynu1YQSPWvZJvMov7DSTiRDXd91GM1cKkyFxpLZUDEzCKb822ym0D30IV8Al+k+UhvHwkmNQ== X-Received: by 2002:a65:5c43:: with SMTP id v3mr17753970pgr.214.1596531058345; Tue, 04 Aug 2020 01:50:58 -0700 (PDT) Received: from [192.168.208.37] ([49.207.138.94]) by smtp.gmail.com with ESMTPSA id k29sm22158632pfp.142.2020.08.04.01.50.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 04 Aug 2020 01:50:57 -0700 (PDT) Subject: Re: Renaming the "master" branch without breaking existing clones To: Junio C Hamano Cc: Matt McCutchen , git@vger.kernel.org References: From: Kaartic Sivaraam Message-ID: <90305e1e-c161-42f3-ab3b-92fc423d17c6@gmail.com> Date: Tue, 4 Aug 2020 14:20:54 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On 04-08-2020 00:17, Junio C Hamano wrote: > Kaartic Sivaraam writes: > >> >> Of course. Though, having a symbolic ref of 'pu/seen' to 'seen' would >> hopefully not defeat the plan while being a little helpful ;) > > How would that be helpful? After all, I do want to allow us accept > a topic about 'seen' from author 'pu', and that pu/seen branch > should be different from the "not yet ready for 'next' but at least > the maintainer acknowledges that he has seen them" integration > branch whose name is 'seen'. > I thought 'seen' was blunt for a topic name in the sense that it doesn't convey what the topic does about 'seen'. So, having a symbolic ref of 'pu/seen' to 'seen' might be a good allusion to the fact that 'pu' has been renamed to 'seen' just by looking at the list of remote branches. -- Sivaraam