From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Bugs in packages which have USE=emacs
Date: Mon, 14 May 2007 14:05:18 +0300 [thread overview]
Message-ID: <4648426E.4020207@gentoo.org> (raw)
In-Reply-To: <20070514120209.42d6e125@luna.home>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
Christian Faulhammer kirjoitti:
> Hi,
>
> As there are quite a lot of packages that have Emacs support by
> USE=emacs, I will just inform you, that the Emacs team would like to be
> informed/cced about issues therein. As we have a bit of experience
> with that monster, we will gladly help to close those bugs instead of
> letting them rot in Bugzilla.
> If the problem is simple we will take the freedom to commit fixes
> ourselves without waiting for maintainers.
>
> V-Li
>
s/without waiting/after giving maintainers a ping/?
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-05-14 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 10:02 [gentoo-dev] Bugs in packages which have USE=emacs Christian Faulhammer
2007-05-14 11:05 ` Petteri Räty [this message]
2007-05-14 11:34 ` [gentoo-dev] " Christian Faulhammer
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=4648426E.4020207@gentoo.org \
--to=betelgeuse@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