From: Eli Zaretskii <eliz@gnu.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: where to report bootstrap bugs? (was: make bootstrap fails from fresh CVS checkout)
Date: Mon, 31 Dec 2007 22:45:24 +0200 [thread overview]
Message-ID: <umyrqwq3f.fsf@gnu.org> (raw)
In-Reply-To: <86abnqwwyk.fsf_-_@lifelogs.com> (message from Ted Zlatanov on Mon, 31 Dec 2007 12:17:07 -0600)
> From: Ted Zlatanov <tzz@lifelogs.com>
> Date: Mon, 31 Dec 2007 12:17:07 -0600
>
> Is there a more appropriate place to ask about `make bootstrap' problems
> from a CVS checkout, if emacs-devel is not it?
emacs-devel _is_ the right place.
> 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.
Try reposting, and thanks.
next prev parent reply other threads:[~2007-12-31 20:45 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 ` where to report bootstrap bugs? (was: make bootstrap fails from fresh CVS checkout) Ted Zlatanov
2007-12-31 20:45 ` Eli Zaretskii [this message]
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
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=umyrqwq3f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.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).