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.3.6/gentoo: 10_all_gcc-default-fortify-source.patch README.history
Date: Thu, 14 Jun 2012 03:53:51 +0000 (UTC)	[thread overview]
Message-ID: <20120614035351.C7AB52004F@flycatcher.gentoo.org> (raw)

vapier      12/06/14 03:53:51

  Modified:             README.history
  Removed:              10_all_gcc-default-fortify-source.patch
  Log:
  drop fortification-enabled-by-default with older (than current stable) compilers as it is hard to maintain when glibc is a moving target, and most people install older compilers for cross-compiling/legacy code anyways

Revision  Changes    Path
1.3                  src/patchsets/gcc/4.3.6/gentoo/README.history

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

Index: README.history
===================================================================
RCS file: /var/cvsroot/gentoo/src/patchsets/gcc/4.3.6/gentoo/README.history,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- README.history	6 Dec 2011 19:10:20 -0000	1.2
+++ README.history	14 Jun 2012 03:53:51 -0000	1.3
@@ -1,3 +1,6 @@
+1.1		[pending]
+	- 10_all_gcc-default-fortify-source.patch
+
 1.0     01 Jul 2011
     + 00_all_gcc-4.1-alpha-mieee-default.patch
 	+ 00_all_gcc-trampolinewarn.patch






                 reply	other threads:[~2012-06-14  3:54 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=20120614035351.C7AB52004F@flycatcher.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