From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: where to report bootstrap bugs? (was: make bootstrap fails from fresh CVS checkout)
Date: Mon, 31 Dec 2007 12:17:07 -0600 [thread overview]
Message-ID: <86abnqwwyk.fsf_-_@lifelogs.com> (raw)
In-Reply-To: 86fxy580db.fsf_-_@lifelogs.com
Is there a more appropriate place to ask about `make bootstrap' problems
from a CVS checkout, if emacs-devel is not it?
After 1.5 months since I submitted a problem report to emacs-devel (I
can't do a bug report because the bootstrap won't build) I haven't heard
anything. While I may be the only one having the problem, my Ubuntu
installation is hardly unusual so other users could be running into this
as well.
Ted
next prev parent reply other threads:[~2007-12-31 18:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 20:35 GNU/Linux (Ubuntu 7.10) bootstrap from a CVS checkout fails ("Maximum buffer size exceeded") Ted Zlatanov
2007-11-30 23:17 ` Ted Zlatanov
2007-12-14 20:52 ` make bootstrap fails from fresh CVS checkout (was: GNU/Linux (Ubuntu 7.10) bootstrap from a CVS checkout fails ("Maximum buffer size exceeded")) Ted Zlatanov
2007-12-31 18:17 ` Ted Zlatanov [this message]
2007-12-31 20:45 ` where to report bootstrap bugs? (was: make bootstrap fails from fresh CVS checkout) Eli Zaretskii
2007-12-31 21:14 ` where to report bootstrap bugs? Michael Albinus
2007-12-31 21:29 ` Ted Zlatanov
2007-12-31 22:15 ` Dan Nicolaescu
2008-01-02 13:30 ` Ted Zlatanov
2008-01-02 13:52 ` Andreas Schwab
2008-01-02 16:42 ` Ted Zlatanov
2008-01-02 17:42 ` Dan Nicolaescu
2008-01-01 3:18 ` where to report bootstrap bugs? (was: make bootstrap fails from fresh CVS checkout) Richard Stallman
2007-12-31 20:57 ` repost of 'make bootstrap' problem " Ted Zlatanov
2008-01-01 1:30 ` repost of 'make bootstrap' problem Thien-Thi Nguyen
2008-01-01 19:48 ` Ted Zlatanov
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=86abnqwwyk.fsf_-_@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.