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=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 66698C47256 for ; Wed, 6 May 2020 03:44:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 342EC2073B for ; Wed, 6 May 2020 03:44:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=pobox.com header.i=@pobox.com header.b="xpUsMZ3k" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726514AbgEFDoF (ORCPT ); Tue, 5 May 2020 23:44:05 -0400 Received: from pb-smtp2.pobox.com ([64.147.108.71]:62265 "EHLO pb-smtp2.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725908AbgEFDoE (ORCPT ); Tue, 5 May 2020 23:44:04 -0400 Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 0BEFF5A073; Tue, 5 May 2020 23:44:04 -0400 (EDT) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=SUa8miPuSscq06vaZ2/vpHt3j/k=; b=xpUsMZ 3kumRa14k2kccSsRFhYBMon2AsCD3jabDCwF82haIn4h3INIc0neWhdj/xyw3ajB 8aTeTxv/vyPoYhSTihhykVVcpek7dunQQ8Y/KjNYgGAj0HvAILY/Zo8oDgZbBywX rtuTLyhzDzyKVJX6a3i8XsctVCeUxojr3ezNA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=DE/1N+XlQcQN6lr69DWFZNClcsJZQrP8 IM+AiKucnCEofmPLi1SrKzf7uM3OQsZv2WXVvA84zuJ+0Pcj6fuGS52Y39iM4Zwd L8xRzcEuIRLAuCM6qBgoWVGjslFFRVH5pRnWvNJsriPLN0J0PatG+kvqg2yTJ0lL XaItjo7ULnM= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id EEE425A071; Tue, 5 May 2020 23:44:03 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.74.119.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 41D1D5A070; Tue, 5 May 2020 23:44:03 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: "Ben Keene via GitGitGadget" Cc: git@vger.kernel.org, Ben Keene Subject: Re: [PATCH] git-p4.py: fix --prepare-p4-only error with multiple commits References: Date: Tue, 05 May 2020 20:44:02 -0700 In-Reply-To: (Ben Keene via GitGitGadget's message of "Fri, 01 May 2020 17:09:12 +0000") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: D426A002-8F4B-11EA-A111-D1361DBA3BAF-77302942!pb-smtp2.pobox.com Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org "Ben Keene via GitGitGadget" writes: > From: Ben Keene > > When using git p4 submit with the --prepare-p4-only option, the program > should prepare a single p4 changelist and notify the user that more > commits are pending and then stop processing. > ... When merged to 'pu', this seems to break builds/tests at Travis CI. Compare a good run with this topic deliberately ejected from 'pu': https://travis-ci.org/github/git/git/builds/683614214 and a bad one with this topic kept in 'pu': https://travis-ci.org/github/git/git/jobs/683604200