From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id B9E9B38A2414 for ; Wed, 18 Mar 2020 21:27:25 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org B9E9B38A2414 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=simark.ca Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=simark@simark.ca Received: from [10.0.0.11] (unknown [192.222.164.54]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 42BE51E5F8; Wed, 18 Mar 2020 17:27:25 -0400 (EDT) Subject: Re: [RFC][PATCH] Support frames inlined into the outer frame To: scott@scottlinder.com, Gdb Patches References: <237802b049d5e89a6d556559815b6f20@scottlinder.com> From: Simon Marchi Message-ID: <94abc873-ed9f-e469-5e5d-56b66ecb847a@simark.ca> Date: Wed, 18 Mar 2020 17:27:24 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Language: en-US-large Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=KAM_DMARC_STATUS, SPF_HELO_PASS, SPF_PASS autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Mar 2020 21:27:26 -0000 On 2020-03-18 5:17 p.m., scott@scottlinder.com wrote: > It was pointed out that posting patches directly to the list is > preferred over Gerrit, so I abandoned the Gerrit review and I'm > attaching the patch here. The wiki says a git-format-patch'd attachment > is OK, but let me know if it isn't the norm! Hi Scott, Doing git-format-patch and attaching the patch is fine, since it pretty much ensures the patch is not mangled by your email client. But really the preferred way is to use "git-send-email". This sends the content of the patch in the body of the email, so it makes it easier to reply, quoting parts of the patch. It also makes it easy to send multiple patches in series. Simon