From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id BE4303858402 for ; Mon, 10 Jan 2022 08:58:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org BE4303858402 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1641805103; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=0mhgKRFYV2dD7MvneULAQS4Hv/hQIWwMcCBGQ3S8NjU=; b=bzaeXQCSIEU19cFH1+OF057M5g32jaOMT7SGBz7fzPRqdWMyyI4nlPFbpVrgWV0ULjFOrw 5TDDSrkG927CkNyDOrU8n3nN9IGNT5OzqvoaninPBLProDkBNtn0KfT1nffpFo4wvT44lg eTXUVqHu6p53MXRSGQM9Gd5heZ8huU8= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-616-6xc3zG-qN5STGjEfjMDoGA-1; Mon, 10 Jan 2022 03:58:21 -0500 X-MC-Unique: 6xc3zG-qN5STGjEfjMDoGA-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 1945B83DD21 for ; Mon, 10 Jan 2022 08:58:21 +0000 (UTC) Received: from calimero.vinschen.de (ovpn-112-6.ams2.redhat.com [10.36.112.6]) by smtp.corp.redhat.com (Postfix) with ESMTPS id DCA486D032 for ; Mon, 10 Jan 2022 08:58:20 +0000 (UTC) Received: by calimero.vinschen.de (Postfix, from userid 500) id 5F99EA80D60; Mon, 10 Jan 2022 09:58:19 +0100 (CET) Date: Mon, 10 Jan 2022 09:58:19 +0100 From: Corinna Vinschen To: newlib@sourceware.org Subject: Re: Error in posix_spawn(3) man page Message-ID: Reply-To: newlib@sourceware.org Mail-Followup-To: newlib@sourceware.org References: MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=vinschen@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-Spam-Status: No, score=-6.8 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: newlib@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Newlib mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2022 08:58:25 -0000 On Jan 7 20:30, Keith Thompson wrote: > On Fri, Jan 7, 2022 at 4:01 PM Keith Thompson > wrote: > > The problem was that I had diff.noprefix=true in my $HOME/.gitconfig. > > It caused `git format-patch` to omit the `a/` and `b/` prefixes, and `git am` > > doesn't appear to have any way to consume a patch with those prefixes missing. > > > > I've attached an updated patch that should apply cleanly. > > > > (I'd argue that this is a git bug, but of course this isn't the place > > to report it.) > > I submitted a Git bug report. The response: > ] The -p flag controls how many segments `git am` or `git apply` > ] removes. The default is -p1. `git am -p0` should apply the patch > ] correctly. > > The "-p" option to "git am" is mentioned in the git-am(1) man page, > but explained only by reference to git-apply(1), so it's easy to miss > (I certainly did). > > My original patch could have been applied with `git am -p0`. I hope > this is useful if you receive any future patches with the same issue. D'oh, thanks! I pushed your patch. Corinna