From: "Daniel Weismüller" <whytea@ipfire.org>
To: development@lists.ipfire.org
Subject: today an IPfire Developer Meeting?
Date: Thu, 15 Nov 2012 13:17:34 +0100 [thread overview]
Message-ID: <50A4DD5E.70209@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 468 bytes --]
Hi there
In case of the latest activities here on the mailing list there are few
things I would like to talk about.
I think it would be helpful to talk to each other directly so I suggest
that we meet us today at 19:30 hours in the IRC developer channel.
Please let me know who will participate.
- Daniel
__________________________________________
You need a firewall?
Easy to use? Powerful? Modular? For free?
www.ipfire.org
An Open Source Firewall Solution
next reply other threads:[~2012-11-15 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 12:17 Daniel Weismüller [this message]
2012-11-15 12:36 ` Michael Tremer
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=50A4DD5E.70209@ipfire.org \
--to=whytea@ipfire.org \
--cc=development@lists.ipfire.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