From: Jeremy Olexa <darkside@gentoo.org>
To: <gentoo-dev@lists.gentoo.org>, <arfrever@gentoo.org>
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/traits: traits-3.4.0.ebuild
Date: Thu, 10 Jun 2010 19:27:40 +0000 [thread overview]
Message-ID: <49b379d145e985fd1d0fe4c57767965a@localhost> (raw)
In-Reply-To: <20100610191934.39FEA2CAD8@corvid.gentoo.org>
On Thu, 10 Jun 2010 19:19:33 +0000 (UTC), "Arfrever Frehtes Taifersar
Arahesis (arfrever)" <arfrever@gentoo.org> wrote:
> arfrever 10/06/10 19:19:33
>
> Modified: traits-3.4.0.ebuild
> Log:
> Fix dependencies. Use -fno-strict-aliasing.
> (Portage version: HEAD/cvs/Linux x86_64)
>
> Revision Changes Path
> 1.3 dev-python/traits/traits-3.4.0.ebuild
I see no reason to *not* add a ChangeLog entry here. Please, consider
the fact that some people don't want to go digging in cvs log to see who
added -fno-strict-aliasing or why. (as an example. I, personally, don't
care about -fno-strict-aliasing)
-Jeremy
next parent reply other threads:[~2010-06-10 19:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100610191934.39FEA2CAD8@corvid.gentoo.org>
2010-06-10 19:27 ` Jeremy Olexa [this message]
2010-06-10 20:00 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/traits: traits-3.4.0.ebuild Arfrever Frehtes Taifersar Arahesis
2010-06-10 20:16 ` Fabian Groffen
2010-06-10 20:25 ` Arfrever Frehtes Taifersar Arahesis
2010-06-10 20:42 ` Nirbheek Chauhan
2010-06-12 15:47 ` Jeroen Roovers
2010-06-10 20:20 ` Nirbheek Chauhan
2010-06-10 20:45 ` Arfrever Frehtes Taifersar Arahesis
2010-06-10 21:45 ` Rémi Cardona
2010-06-11 6:51 ` Alex Alexander
2010-06-11 8:43 ` Alexis Ballier
2010-06-19 20:53 ` Mike Frysinger
2010-06-20 13:55 ` Arfrever Frehtes Taifersar Arahesis
2010-06-20 16:05 ` [gentoo-dev] " Peter Hjalmarsson
2010-06-20 22:27 ` [gentoo-dev] " Mike Frysinger
2010-06-21 4:01 ` Brian Harring
2010-06-21 21:28 ` Arfrever Frehtes Taifersar Arahesis
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=49b379d145e985fd1d0fe4c57767965a@localhost \
--to=darkside@gentoo.org \
--cc=arfrever@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