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 E6BBA3858281 for ; Fri, 27 Jan 2023 22:04:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org E6BBA3858281 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=1674857040; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=xteqWX8+T4J9I4F9SJTsPns+LCGpl7dP7oycqwcKmSY=; b=GrlY0WT8+pD5Ux8r5Ez29KsZsJTlp5Pr8fcjZ+t6+jap3mPvwE4StF+2pneqApj5Ifcs6X 56cG1QPz1YPt4trgd7vau7t6I3GYydLtxLr0hdpIhxL9XDXVQddAj/WzsBQs1B6iAnjrQJ wU8QgddnYrVZvAInh1boVEvx4zjetpo= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-306-hYks6qTbOnmHHoZlaYpWig-1; Fri, 27 Jan 2023 17:03:58 -0500 X-MC-Unique: hYks6qTbOnmHHoZlaYpWig-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 858B91818E49; Fri, 27 Jan 2023 22:03:58 +0000 (UTC) Received: from f37-zws-1 (unknown [10.2.16.229]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 2515A14171C2; Fri, 27 Jan 2023 22:03:58 +0000 (UTC) Date: Fri, 27 Jan 2023 15:03:56 -0700 From: Kevin Buettner To: Tom de Vries Cc: gdb-patches@sourceware.org, pedro@palves.net Subject: Re: [PATCH v4 0/8] Fix gdb.base/gdb-sigterm.exp failure/error Message-ID: <20230127150356.0cd024c2@f37-zws-1> In-Reply-To: <939427f4-8b1f-1230-78d9-85d3aa3d7ac5@suse.de> References: <20230112015630.32999-1-kevinb@redhat.com> <939427f4-8b1f-1230-78d9-85d3aa3d7ac5@suse.de> Organization: Red Hat MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Thu, 12 Jan 2023 13:37:00 +0100 Tom de Vries wrote: > FWIW, I ran into this when applying: > ... > $ git am ~/patches/grouped/eml/* > Applying: Introduce gdb_exception_forced_quit > Applying: Handle gdb SIGTERM by throwing / catching gdb_exception_force_quit > .git/rebase-apply/patch:37: indent with spaces. > { > warning: 1 line adds whitespace errors. > Applying: Catch gdb_exception_error instead of gdb_exception (in many > places) > Applying: Python QUIT processing updates > Applying: Guile QUIT processing updates > Applying: Call quit_force for gdb_exception_forced_quit in > safe_execute_command > Applying: QUIT processing w/ explicit throw for gdb_exception_forced_quit > .git/rebase-apply/patch:17: indent with spaces. > throw; > .git/rebase-apply/patch:46: indent with spaces. > { > .git/rebase-apply/patch:58: indent with spaces. > { > warning: 3 lines add whitespace errors. > Applying: Forced quit cases handled by resetting sync_quit_force_run > .git/rebase-apply/patch:41: indent with spaces. > to newline, so, for this case, reset the quit flag for > warning: 1 line adds whitespace errors. > ... Thanks! I've fixed these whitespace problems in my local sources. I've also added a "Tested-by" attribution for you to each commit message. Kevin