From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Not reading bugzilla email anymore
Date: Sat, 20 Sep 2003 19:42:44 +0300 [thread overview]
Message-ID: <200309201942.44317.danarmak@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
Hi all,
I hope things are going well in my absence :-) In fact I know they are, since
I'm still reading -dev and -core (and personal email). But I won't be reading
bugzilla notifications anymore, since there's such a lot of them for kde@g.o.
In the (highly improbable) event anyone should need me, please write directly
to danarmak@g.o, cc's on bugzilla will still be ignored.
Over here everything's fine, and I trust I'll be able to return to active
Gentoo developement sometime in the winter. Take care everyone,
--
Dan Armak
Gentoo Linux developer (KDE)
Matan, Israel
Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key
Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD 0069 508D 9143 8D5F 8951
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2003-09-20 16:42 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=200309201942.44317.danarmak@gentoo.org \
--to=danarmak@gentoo.org \
--cc=gentoo-dev@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