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=-3.6 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,RCVD_IN_DNSWL_BLOCKED, 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 B8BFD1F934 for ; Mon, 11 Jan 2021 20:25:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2404196AbhAKUXo (ORCPT ); Mon, 11 Jan 2021 15:23:44 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57568 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389284AbhAKUXn (ORCPT ); Mon, 11 Jan 2021 15:23:43 -0500 Received: from mail-oi1-x230.google.com (mail-oi1-x230.google.com [IPv6:2607:f8b0:4864:20::230]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 74AE6C061786 for ; Mon, 11 Jan 2021 12:23:03 -0800 (PST) Received: by mail-oi1-x230.google.com with SMTP id d203so732426oia.0 for ; Mon, 11 Jan 2021 12:23:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xpXkOnut7iytBXwQ/GB3UhTM8tqnJzSlLhcKd7jermk=; b=EWE0nzmQs9y8muwN98YhACwnvJLUuJuL7P66O1UECk5n9FJUY0Hef4bx5FGcT6/9of 0nW7Y8i8vR6n8UbWvOD0yp4PuIQ2p4eCno5WM+iZieH0t6LFSmqU8O+dwWodc0aBeayZ ODjQykQCKcwDsDMnAcjAwAWpOyf+wCyGHAwHFVpE1AyO1ejlPGMDIoiThdlkVHTVJcvV 4E+w3+9FKja1JJzUKissOG+kJO07cu/6HHHD0BZD6xiveY+MIZyLefMDv9+1+eM+Qseo 7CqMypg6Ho6uHuNk74yd90OlSV6AuqZDp6dqxgf/xEq0DZBALdT3t/IFd5772+Bacos4 FLZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xpXkOnut7iytBXwQ/GB3UhTM8tqnJzSlLhcKd7jermk=; b=dXwGpKwdugbxv8dkUyG10p7twJ2LBEbcYPtjgYnGsZrBQ072qtWajHvD6srzfCVwKS PQPcrcEadiadXtvQxmdDFgtaX77ZWJL3KXtbnVJuIAB2sKmWGnaixQ+Y5qYz5aapnLPr lnDoVOhVhwumyKhdCWg1yycgzEf1Ml7NOKsaia9V1sNgE8xLpetc5yA3EboZ87Up1iMl tb2W84Ee8651tcKQuKHUcFr/a9N+6eLI/jwp/yoFw7x3yKc5u8fMYjmKdnKM+Io+dCjw Av+4iDZMVk6zQPRF/klMExVHtZA5QjzcoQy/TRq73jybISAUBaM2a+92cHiu5ouUJHNP SoyA== X-Gm-Message-State: AOAM533FsX0hyE+hqqyhCwtz7Xv2ZWHe3yQve9A4eV1vW/sNa+XR7Rrk P1BcvR6BmQhZeNO8M0i3b3KaRGZjood02lj5xw8= X-Google-Smtp-Source: ABdhPJxFALhf3G+nkpon5tBUP9GOa9esqrTf+tikck8XCzRHixAlROrvGmjJFKmnjRz+YhTnE5+2x2wMPnF8cwjx2ow= X-Received: by 2002:aca:3145:: with SMTP id x66mr347822oix.29.1610396582602; Mon, 11 Jan 2021 12:23:02 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Nipunn Koorapati Date: Mon, 11 Jan 2021 20:22:51 +0000 Message-ID: Subject: Re: [PATCH v5 0/2] negative-refspec: fix segfault on : refspec To: Junio C Hamano Cc: Nipunn Koorapati via GitGitGadget , Git List , Eric Sunshine Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org > Eventually by backporting, but a fix typically goes to the current > development track first so it would happen after 2.30 is finished, I > would think. I wanted to bump this idea - now that it appears that 2.30 is complete and the new maint branch. Given that this patch makes matching-refspec unusable in 2.29, would it make sense to backport a fix to the 2.29 release? If that seems risky/unwanted, is there some practice of documenting known (serious) bugs in past releases? Thanks --Nipunn