public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-desktop@lists.gentoo.org,
	gentoo-dev-announce@lists.gentoo.org,
	gentoo-dev@lists.gentoo.org, kde@gentoo.org
Subject: [gentoo-dev-announce] next Gentoo KDE team meeting Thu 2013-05-23 19:00 UTC
Date: Fri, 17 May 2013 21:02:53 +0200	[thread overview]
Message-ID: <3149297.pUuD68LypC@grenadine> (raw)

[-- Attachment #1: Type: text/plain, Size: 296 bytes --]


Hi everyone, 

the next Gentoo KDE team meeting takes place
Thu 2013-05-23 19:00 UTC
as always on the freenode channel #gentoo-meetings

Agenda: http://wiki.gentoo.org/wiki/Project:KDE/Meeting/2013-05

Cheers, 
Andreas

-- 
Andreas K. Huettel
Gentoo Linux developer
kde, sci, arm, tex, printing

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 966 bytes --]

                 reply	other threads:[~2013-05-17 19:24 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=3149297.pUuD68LypC@grenadine \
    --to=dilfridge@gentoo.org \
    --cc=gentoo-desktop@lists.gentoo.org \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=kde@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