X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org X-Envelope-From: sledz AT zone42 DOT org X-Envelope-To: Message-ID: <4997FDA9.5080808@zone42.org> Date: Sun, 15 Feb 2009 12:34:01 +0100 From: Steffen Sledz User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Emacs maintainer [was Re: POP Rmail in Emacs] References: <494C1451 DOT 5050703 AT alice DOT it> <494C307C DOT 6020604 AT cornell DOT edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Eli Zaretskii wrote: > Let me rephrase: we need a more active maintainer of the Cygwin Emacs. > > As a matter of fact, reports of Cygwin-related problems on the Emacs > development and bug-reporting lists don't get any responses from > Steffen Sledz. Searching the emacs-devel and bug-gnu-emacs archives > for his name yields zero hits. I'm really sorry for my low activity. I'm a bit depressed because of my unsuccessful fighting with the build system (see some other threads in cygwin-apps). This detained (and detains) me from working on the emacs problems. But i hope there will come better times. Also my try to take over maintainership for emacs was made out of necessity because no one else was willing to do this. And i don't want to see emacs vanish from cygwin. May be the task is a bit to big for me. So if there is somebody else interested in taking over the maintainership or to share it with me, you're welcome. Steffen -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/