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: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-3.8 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id EE2001F466 for ; Mon, 20 Jan 2020 20:08:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726876AbgATUI3 (ORCPT ); Mon, 20 Jan 2020 15:08:29 -0500 Received: from mail-wr1-f67.google.com ([209.85.221.67]:39777 "EHLO mail-wr1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726843AbgATUI3 (ORCPT ); Mon, 20 Jan 2020 15:08:29 -0500 Received: by mail-wr1-f67.google.com with SMTP id y11so795457wrt.6 for ; Mon, 20 Jan 2020 12:08:27 -0800 (PST) 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=7Tgi6woUaIufW+iBPVATkW9DEyGJARg6YikJGZTpTk8=; b=sJpCt1iXjkdFvQJLYxpC/Z3b+SxAj+bwVRDU2ra9XZgOqECoPis93c1UaelnSDn3QI u2m17HuVm6url3ECu7in/frUm1a57PfZWknBZganVjMBbrNpNEaVV7WfsuoLZ0JZNbml HdVDL+6l8n+Xs9J0IxM+gU39OHwYNwM3XB2d397dFAKRhkTCK4Xay5DSGnyR4A/QpfK5 N4HTXvtGEMbJSzfTWRItG+eGM4fqv5mz85kV7vZ+8vnCTHYq15iwWo0DgYKvp9xyJyQG 1fZm+AhLmsJ7VsFz4xbI6jOVuNThB7XnFAZLMau4fiLyoZD9GT4IpLm5FQ/2eT7wQqWB xbBQ== X-Gm-Message-State: APjAAAXavP9+qHKzhDKLmv0chcWwuIZdiDr7L+WE6EptchbPeQxvWdi9 FAkreQ1vVnwEVJJw8/812hYOchtlJ0tOFuNS90M= X-Google-Smtp-Source: APXvYqxpaEIf2O7ckY/gI1L/vXZ8SgI5aal9EhxSEymuR0CwKwYYLJ67G2REwUg8nB2iAqHzxj/eUbBgCYnnXtwwvYs= X-Received: by 2002:adf:ee52:: with SMTP id w18mr1137487wro.415.1579550906788; Mon, 20 Jan 2020 12:08:26 -0800 (PST) MIME-Version: 1.0 References: <102fa568dc09c1faa2d36903ccb7e1b285dd50b2.1579304283.git.gitgitgadget@gmail.com> In-Reply-To: From: Eric Sunshine Date: Mon, 20 Jan 2020 15:08:15 -0500 Message-ID: Subject: Re: [PATCH v2 2/3] rebase -i: re-fix short SHA-1 collision To: Johannes Schindelin Cc: Johannes Schindelin via GitGitGadget , Git List , "brian m. carlson" , Alban Gruin , Junio C Hamano Content-Type: text/plain; charset="UTF-8" Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Mon, Jan 20, 2020 at 3:04 PM Johannes Schindelin wrote: > On Mon, 20 Jan 2020, Eric Sunshine wrote: > > On Fri, Jan 17, 2020 at 6:38 PM Johannes Schindelin via GitGitGadget > > wrote: > > > + test $colliding_sha1 = "$(git rev-parse HEAD | cut -c 1-7)" && > > > > How much do we care that this is introducing new code with git > > upstream of a pipe (considering recent efforts to eradicate such > > usage)? Same question regarding several other new instances introduce > > by this patch. > > I would argue that the test case will fail if the `git` call fails. So I > am not overly concerned if that `git` call is upstream of a pipe. Unless the git command crashes _after_ it produces the correct output...