From: Joel Brobecker <brobecker@adacore.com>
To: "Tedeschi, Walfred" <walfred.tedeschi@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [pushed] [PATCH V4] Add support for bound table in the Intel MPX context.
Date: Wed, 10 Jun 2015 11:54:00 -0000 [thread overview]
Message-ID: <20150610115430.GA11014@adacore.com> (raw)
In-Reply-To: <AC542571535E904D8E8ADAE745D60B194441FE34@IRSMSX102.ger.corp.intel.com>
> I followed your suggestion and pushed as considering that the rest was ok.
> Hope this is fine.
This isn't exactly how I meant it, but that's fine :-).
I saw that you pushed the ChangeLog entries separately. I assume
this was just an oversight? Normally, we'd ask that they be pushed
within the corresponding commit. Just making sure...
--
Joel
next prev parent reply other threads:[~2015-06-10 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 8:37 Tedeschi, Walfred
2015-06-10 11:54 ` Joel Brobecker [this message]
2015-06-10 11:56 ` Tedeschi, Walfred
2015-06-11 17:25 ` [BUILDROBOT] makeinfo fails (was: [pushed] [PATCH V4] Add support for bound table in the Intel MPX context.) Jan-Benedict Glaw
2015-06-11 18:12 ` Joel Brobecker
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=20150610115430.GA11014@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=walfred.tedeschi@intel.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).