From: "Mark Loeser (halcy0n)" <halcy0n@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in sys-devel/gcc: ChangeLog gcc-4.4.1.ebuild
Date: Thu, 23 Jul 2009 06:02:48 +0000 [thread overview]
Message-ID: <E1MTrOC-0001ap-18@stork.gentoo.org> (raw)
halcy0n 09/07/23 06:02:48
Modified: ChangeLog gcc-4.4.1.ebuild
Log:
Bump uclibc patchset to fix a digest screwup
(Portage version: 2.2_rc33/cvs/Linux x86_64)
Revision Changes Path
1.715 sys-devel/gcc/ChangeLog
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-devel/gcc/ChangeLog?rev=1.715&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-devel/gcc/ChangeLog?rev=1.715&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-devel/gcc/ChangeLog?r1=1.714&r2=1.715
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/sys-devel/gcc/ChangeLog,v
retrieving revision 1.714
retrieving revision 1.715
diff -u -r1.714 -r1.715
--- ChangeLog 23 Jul 2009 01:57:28 -0000 1.714
+++ ChangeLog 23 Jul 2009 06:02:47 -0000 1.715
@@ -1,6 +1,9 @@
# ChangeLog for sys-devel/gcc
# Copyright 1999-2009 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/sys-devel/gcc/ChangeLog,v 1.714 2009/07/23 01:57:28 halcy0n Exp $
+# $Header: /var/cvsroot/gentoo-x86/sys-devel/gcc/ChangeLog,v 1.715 2009/07/23 06:02:47 halcy0n Exp $
+
+ 23 Jul 2009; Mark Loeser <halcy0n@gentoo.org> gcc-4.4.1.ebuild:
+ Bump uclibc patchset to fix a digest screwup
*gcc-4.4.1 (23 Jul 2009)
1.2 sys-devel/gcc/gcc-4.4.1.ebuild
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-devel/gcc/gcc-4.4.1.ebuild?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-devel/gcc/gcc-4.4.1.ebuild?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-devel/gcc/gcc-4.4.1.ebuild?r1=1.1&r2=1.2
Index: gcc-4.4.1.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/sys-devel/gcc/gcc-4.4.1.ebuild,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- gcc-4.4.1.ebuild 23 Jul 2009 01:57:28 -0000 1.1
+++ gcc-4.4.1.ebuild 23 Jul 2009 06:02:47 -0000 1.2
@@ -1,9 +1,9 @@
# Copyright 1999-2009 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/sys-devel/gcc/gcc-4.4.1.ebuild,v 1.1 2009/07/23 01:57:28 halcy0n Exp $
+# $Header: /var/cvsroot/gentoo-x86/sys-devel/gcc/gcc-4.4.1.ebuild,v 1.2 2009/07/23 06:02:47 halcy0n Exp $
PATCH_VER="1.0"
-UCLIBC_VER="1.0"
+UCLIBC_VER="1.1"
ETYPE="gcc-compiler"
next reply other threads:[~2009-07-23 6:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 6:02 Mark Loeser (halcy0n) [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-20 5:26 [gentoo-commits] gentoo-x86 commit in sys-devel/gcc: ChangeLog gcc-4.4.1.ebuild Ryan Hill (dirtyepic)
2009-09-20 4:36 Ryan Hill (dirtyepic)
2009-09-19 23:36 Alexis Ballier (aballier)
2009-08-16 14:49 Raul Porcel (armin76)
2009-08-13 20:07 Mark Loeser (halcy0n)
2009-07-24 20:23 Robert Piasek (dagger)
2009-07-24 15:23 Joseph Jezak (josejx)
2009-07-23 1:57 Mark Loeser (halcy0n)
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=E1MTrOC-0001ap-18@stork.gentoo.org \
--to=halcy0n@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