From: Sven Joachim <svenjoac@gmx.de>
To: emacs-devel@gnu.org
Cc: Eric Hanchrow <eric.hanchrow@gmail.com>
Subject: Re: recent checkin broke the Emacs build
Date: Fri, 13 Feb 2009 11:03:16 +0100 [thread overview]
Message-ID: <87iqneodqz.fsf@turtle.gmx.de> (raw)
In-Reply-To: <871vu2x0g3.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Fri, 13 Feb 2009 08:25:48 +0100")
On 2009-02-13 08:25 +0100, Tassilo Horn wrote:
> I suffered from the error before and your patch works fine for me. Is
> there any reason not to check it in?
It requires somebody with write access.
Sven
next prev parent reply other threads:[~2009-02-13 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <36366a980902102137p3f495058hfb9bb9eb827edca@mail.gmail.com>
2009-02-12 4:42 ` recent checkin broke the Emacs build Eric Hanchrow
2009-02-12 8:33 ` Sven Joachim
2009-02-13 7:25 ` Tassilo Horn
2009-02-13 10:03 ` Sven Joachim [this message]
2009-02-13 10:21 ` Tassilo Horn
2009-02-13 14:23 ` Chong Yidong
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iqneodqz.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=eric.hanchrow@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).