From: "Johannes Huber" <johu@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/kde:master commit in: Documentation/maintainers/meetings/
Date: Tue, 7 Aug 2012 22:12:26 +0000 (UTC) [thread overview]
Message-ID: <1344377508.8bd3f43bd16d402e55a5c863f14e4a7ea19156b6.johu@gentoo> (raw)
commit: 8bd3f43bd16d402e55a5c863f14e4a7ea19156b6
Author: Johannes Huber <johu <AT> gentoo <DOT> org>
AuthorDate: Tue Aug 7 22:11:48 2012 +0000
Commit: Johannes Huber <johu <AT> gentoo <DOT> org>
CommitDate: Tue Aug 7 22:11:48 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=commit;h=8bd3f43b
[meetings] bug++
---
Documentation/maintainers/meetings/meeting-2012-08 | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/Documentation/maintainers/meetings/meeting-2012-08 b/Documentation/maintainers/meetings/meeting-2012-08
index 7219005..6d87aeb 100644
--- a/Documentation/maintainers/meetings/meeting-2012-08
+++ b/Documentation/maintainers/meetings/meeting-2012-08
@@ -16,6 +16,9 @@ Agenda topics for the next KDE team meeting
access to a box to test if they are still useful?
4. Bugs (30 minutes)
+ * kde-base/kmail-4.9.0 fails compiling with gcc-4.4.7
+ https://bugs.gentoo.org/show_bug.cgi?id=429742
+
* app-cdr/k3b: Excessive use of REQUIRED_USE (and wrong combination
USE="lame"+"encode") REQUIRED_USE was added, otherwise USE="-encode lame"
does nothing. https://bugs.gentoo.org/show_bug.cgi?id=417235
next reply other threads:[~2012-08-07 22:12 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 22:12 Johannes Huber [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-08 18:43 [gentoo-commits] proj/kde:master commit in: Documentation/maintainers/meetings/ Johannes Huber
2012-08-14 13:28 Michael Palimaka
2012-08-10 8:03 Johannes Huber
2012-08-09 10:36 Johannes Huber
2012-08-06 10:03 Johannes Huber
2012-07-21 16:51 Michael Palimaka
2012-07-13 22:31 Johannes Huber
2012-06-20 21:39 Andreas Hüttel
2012-06-16 9:01 Andreas Hüttel
2012-06-13 19:58 Andreas Hüttel
2012-06-13 17:16 Michael Palimaka
2012-05-17 18:53 Michael Palimaka
2012-05-17 18:41 Andreas Hüttel
2012-05-17 13:00 Johannes Huber
2012-05-17 10:03 Michael Palimaka
2012-05-10 15:23 Chris Reffett
2012-05-09 15:07 Michael Palimaka
2012-05-08 16:29 Andreas Hüttel
2012-04-15 18:10 Andreas Hüttel
2012-03-19 9:25 Theo Chatzimichos
2012-01-14 15:02 Andreas Hüttel
2012-01-14 14:52 Maciej Mrozowski
2012-01-13 20:36 Andreas Hüttel
2012-01-13 20:19 Andreas Hüttel
2012-01-13 19:46 Johannes Huber
2012-01-11 17:13 Johannes Huber
2012-01-08 19:43 Andreas Hüttel
2012-01-06 18:48 Johannes Huber
2011-10-14 19:21 Andreas Hüttel
2011-10-06 22:51 Andreas Hüttel
2011-08-29 21:52 Andreas Hüttel
2011-08-28 22:56 Andreas Hüttel
2011-08-28 21:03 Maciej Mrozowski
2011-08-27 21:35 Andreas Hüttel
2011-08-23 21:30 Andreas Hüttel
2011-06-01 2:21 Jorge Manuel B. S. Vicetto
2011-05-29 21:38 Andreas Hüttel
2011-05-29 17:28 Andreas Hüttel
2011-05-21 19:19 Andreas K. Huettel
2011-03-24 11:19 Theo Chatzimichos
2011-03-24 1:22 Andreas K. Huettel
2011-02-10 18:53 Theo Chatzimichos
2011-02-09 14:50 Theo Chatzimichos
2011-02-09 14:37 Tomas Chvatal
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=1344377508.8bd3f43bd16d402e55a5c863f14e4a7ea19156b6.johu@gentoo \
--to=johu@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