unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jarek Czekalski <jarekczek@poczta.onet.pl>
To: emacs-devel@gnu.org
Subject: Re: emacs freezes - how to troubleshoot, build with assertions
Date: Sat, 02 Nov 2013 15:22:21 +0100	[thread overview]
Message-ID: <52750A9D.60706@poczta.onet.pl> (raw)
In-Reply-To: <83txfv9d92.fsf@gnu.org>

W dniu 11/02/2013 01:52 PM, Eli Zaretskii pisze:
> That is always the preferred way, when you are running the development 
> code.

Please tell me how to do it. Can't find it in the files you pointed out.

> Is the above the starting point you were looking for? If not, please 
> elaborate about what would you like to find as a starting point. 

There are several places which a new developer should visit. Some I know 
(you told me about them today) are these:
1. Info "Sending patches"
2. etc directory

I would like these places to be mentioned in a development wiki. The 
wiki could be placed (or at list linked to) at savannah, as savannah is 
the place linked to directly from gnu.org/software/emacs. If someone 
complains about missing info, it would be added to wiki. Soon wiki 
becomes a good starting point. The time required to build it is like 
half an hour.

For example I started to gather some info here:
https://sourceforge.net/p/emacspeakwin/wiki/Development%20Information/
In simplest case this wiki page may be renamed to "Emacs developer's 
guide" and linked from savannah as "See also Emacs Developer's Guide".

Jarek




  reply	other threads:[~2013-11-02 14:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-02 12:22 emacs freezes - how to troubleshoot, build with assertions Jarek Czekalski
2013-11-02 12:52 ` Eli Zaretskii
2013-11-02 14:22   ` Jarek Czekalski [this message]
2013-11-02 16:22     ` Eli Zaretskii
2013-11-03  0:16     ` Xue Fuqiao

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=52750A9D.60706@poczta.onet.pl \
    --to=jarekczek@poczta.onet.pl \
    --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 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).