Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10961] [Buildroot 2018.02] Grub2 fails to build for x86_64 when BR2_SSP_ALL is enabled
Date: Thu, 19 Apr 2018 08:35:52 +0000	[thread overview]
Message-ID: <bug-10961-163-AUKMDn735z@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10961-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=10961

--- Comment #2 from Tarek El-Sherbiny <tarek_el-sherbiny@waters.com> ---
Hi Yann,

Thanks for getting back to me. I certainly would like to submit the patch to
the mailing list.
The reason I didn't because my corporate  mail server forces this
confidentiality footer at the bottom of any email:

=========================================================== The information in
this email is confidential, and is intended solely for the addressee(s). Access
to this email by anyone else is unauthorized and therefore prohibited. If you
are not the intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited and may be unlawful.
===========================================================

I asked the IT and legal departments if we can have a different policy for
opensource community but they did not welcome the idea.


I will just submit the patch anyway ....

Best Regards,
Tarek

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2018-04-19  8:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17  9:04 [Buildroot] [Bug 10961] New: [Buildroot 2018.02] Grub2 fails to build for x86_64 when BR2_SSP_ALL is enabled bugzilla at busybox.net
2018-04-17 17:33 ` [Buildroot] [Bug 10961] " bugzilla at busybox.net
2018-04-19  8:35 ` bugzilla at busybox.net [this message]
2018-04-19 21:33 ` bugzilla at busybox.net

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=bug-10961-163-AUKMDn735z@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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