From: Reiner Steib <reinersteib+from-uce@imap.cc>
Subject: Re: cvs-version - how to build?
Date: Wed, 06 Apr 2005 18:30:06 +0200 [thread overview]
Message-ID: <v9ekdnookx.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: 4253f696$0$315$ba620e4c@news.skynet.be
On Wed, Apr 06 2005, Helmut Jarausch wrote:
> I've been trying to build the cvs-version several times,
> but it always fails.
,----[ emacs/INSTALL.CVS ]
| Questions, requests, and bug reports about the CVS versions of Emacs
| should be sent to emacs-pretest-bug@gnu.org rather than gnu.emacs.help
| or gnu.emacs.bug. Ideally, use M-x report-emacs-bug RET which will
| send it to the proper place.
`----
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2005-04-06 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 14:47 cvs-version - how to build? Helmut Jarausch
2005-04-06 16:30 ` Reiner Steib [this message]
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=v9ekdnookx.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+from-uce@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).