unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Xue Fuqiao <xfq.free@gmail.com>
To: Jarek Czekalski <jarekczek@poczta.onet.pl>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: emacs freezes - how to troubleshoot, build with assertions
Date: Sun, 3 Nov 2013 08:16:22 +0800	[thread overview]
Message-ID: <CAAF+z6FFdrLJze7AL+gwh7iw3+C9His0A+nU9j_qKHBVtOzfNA@mail.gmail.com> (raw)
In-Reply-To: <52750A9D.60706@poczta.onet.pl>

On Sat, Nov 2, 2013 at 10:22 PM, Jarek Czekalski
<jarekczek@poczta.onet.pl> wrote:
> 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

And these ones (at least), I think:

http://www.gnu.org/prep/standards/
https://www.gnu.org/prep/maintain/html_node/Legal-Matters.html#Legal-Matters
http://www.emacswiki.org/emacs/BzrForEmacsDevs
(info "(elisp) Tips")
admin/notes

> 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.

I wrote a contributing guide[fn:1] before, but I deleted it later
because it is too verbose[fn:2].  I plan to write some other things
about contributing to Emacs now: an Emacs Lisp refcard, an Emacs Lisp
FAQ, and an Emacs hacker guide[fn:3].

Footnotes:

[fn:1] http://lists.gnu.org/archive/html/emacs-devel/2013-04/msg00604.html

[fn:2] http://lists.gnu.org/archive/html/emacs-devel/2013-04/msg00659.html

[fn:3] Only for Emacs Dev, so it is not like the one above.  Many people
       in Emacs Dev have expressed their wish for this document, like:
       http://lists.gnu.org/archive/html/emacs-devel/2013-04/msg00660.html
       http://lists.gnu.org/archive/html/emacs-devel/2013-09/msg00616.html

-- 
Best regards, Xue Fuqiao.
http://www.gnu.org/software/emacs/



      parent reply	other threads:[~2013-11-03  0:16 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
2013-11-02 16:22     ` Eli Zaretskii
2013-11-03  0:16     ` Xue Fuqiao [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=CAAF+z6FFdrLJze7AL+gwh7iw3+C9His0A+nU9j_qKHBVtOzfNA@mail.gmail.com \
    --to=xfq.free@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=jarekczek@poczta.onet.pl \
    /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).