Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alan Hayward <Alan.Hayward@arm.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: "Pavel I. Kryukov" <kryukov@frtk.ru>,
	GDB Patches	<gdb-patches@sourceware.org>, nd <nd@arm.com>
Subject: Re: [PATCH] Simulator: prevent inlining in C++ mode
Date: Thu, 17 Jan 2019 09:53:00 -0000	[thread overview]
Message-ID: <C6EB390D-9471-4A94-BE1B-87B2217BA4E2@arm.com> (raw)
In-Reply-To: <1d3c4bfafaf0782637c402c8c13041bf@polymtl.ca>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1197 bytes --]


> On 16 Jan 2019, at 19:51, Simon Marchi <simon.marchi@polymtl.ca> wrote:
> 
> On 2019-01-16 13:29, Pavel I. Kryukov wrote:
>> Okay, there are no C++ compiler errors other than macro expansion,
>> so this patch may be ignored. I submitted a separate patch for macros
>> expansion (https://sourceware.org/ml/gdb-patches/2019-01/msg00367.html)
> 
> I'll take a look.
> 
>> (Sorry, I still get lines wrapped in patches while sending them via Gmail.
>> Could you please tell if there is a workaround?)
> 
> The best way is to use "git-send-email".  You will need an SMTP server, whether it is gmail, your ISP's, etc.  This should help:
> 
> https://coderwall.com/p/dp-gka/setting-up-git-send-email-with-gmail
> 
> If you really can't get this to work, the next best thing is to generate a .patch file (git format-patch HEAD^) and send it as an attachment.  This ensures that the formatting is preserved.
> 

As someone who suffered similar issues until I moved to git send-mail, I’m
wondering if it’s worth it adding to the "Submitting Patches” section in
the CONTRIBUTE file?  I can have a go at writing that if it makes sense.


Alan.\x16º&Öéj×!zÊÞ¶êçםùÓ¹b²Ö«r\x18\x1dn–­r\x17¬

  reply	other threads:[~2019-01-17  9:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11  9:59 Павел Крюков
2019-01-15 23:07 ` Simon Marchi
2019-01-15 23:31   ` Павел Крюков
2019-01-16 18:29     ` Pavel I. Kryukov
2019-01-16 19:51       ` Simon Marchi
2019-01-17  9:53         ` Alan Hayward [this message]
2019-01-17 13:20           ` Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C6EB390D-9471-4A94-BE1B-87B2217BA4E2@arm.com \
    --to=alan.hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kryukov@frtk.ru \
    --cc=nd@arm.com \
    --cc=simon.marchi@polymtl.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox