From: Chris Reffett <creffett@gentoo.org>
To: gentoo-desktop@lists.gentoo.org
Cc: kde@gentoo.org, gentoo-dev-announce@lists.gentoo.org,
scarabeus@gentoo.org
Subject: [gentoo-dev-announce] January 2013 KDE team meeting
Date: Mon, 14 Jan 2013 16:54:11 -0500 [thread overview]
Message-ID: <50F47E83.90907@gentoo.org> (raw)
In-Reply-To: <50999FB6.4000705@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello all,
This month's KDE team meeting will be Thursday, Jan 17 at 1900 UTC in
#gentoo-meetings. The agenda is up at
http://wiki.gentoo.org/wiki/Project:KDE/Meeting/2013-1. All are
welcome to attend the meeting.
Chris Reffett
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlD0foMACgkQ23laikJhg1RIVACgiK9U5WXCqU9Iwkp8e+MQgPsP
RPcAniUYZAgGYYUWx8P21OOjagvEBkvs
=XzZ9
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-01-14 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 10:50 [gentoo-dev-announce] August 2012 KDE team meeting Michael Palimaka
2012-09-20 19:40 ` [gentoo-dev-announce] " Chris Reffett
2012-11-06 23:39 ` [gentoo-dev-announce] November " Chris Reffett
2013-01-14 21:54 ` Chris Reffett [this message]
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=50F47E83.90907@gentoo.org \
--to=creffett@gentoo.org \
--cc=gentoo-desktop@lists.gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=kde@gentoo.org \
--cc=scarabeus@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