public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Frysinger (vapier)" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in src/patchsets/gcc/4.6.3/gentoo: 10_all_default-fortify-source.patch README.history
Date: Wed, 13 Jan 2016 05:01:47 +0000 (UTC)	[thread overview]
Message-ID: <20160113050147.2B76BEEF@oystercatcher.gentoo.org> (raw)

vapier      16/01/13 05:01:47

  Modified:             README.history
  Removed:              10_all_default-fortify-source.patch
  Log:
  stop enabling -D_FORTIFY_SOURCE by default in older versions for compatibility and simplicity -- these are really only used for old builds now and cross-compiling

Revision  Changes    Path
1.26                 src/patchsets/gcc/4.6.3/gentoo/README.history

file : http://sources.gentoo.org/viewvc.cgi/gentoo/src/patchsets/gcc/4.6.3/gentoo/README.history?rev=1.26&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/src/patchsets/gcc/4.6.3/gentoo/README.history?rev=1.26&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/src/patchsets/gcc/4.6.3/gentoo/README.history?r1=1.25&r2=1.26

Index: README.history
===================================================================
RCS file: /var/cvsroot/gentoo/src/patchsets/gcc/4.6.3/gentoo/README.history,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- README.history	13 Jan 2016 04:55:24 -0000	1.25
+++ README.history	13 Jan 2016 05:01:47 -0000	1.26
@@ -1,4 +1,5 @@
 1.14	[pending]
+	- 10_all_default-fortify-source.patch
 	- 12_all_default-warn-trampolines.patch
 	- 74_all_gcc46_cloog-dl.patch
 





                 reply	other threads:[~2016-01-13  5:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160113050147.2B76BEEF@oystercatcher.gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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