From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: Emacs development
Date: Sat, 21 Feb 2015 19:28:34 +0800 [thread overview]
Message-ID: <87oaon7bbx.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87385zo9vr.fsf@topper.koldfront.dk
asjo@koldfront.dk (Adam Sjøgren) writes:
> Alexis writes:
>
>> On 2015-02-21T13:36:20+1100, Sam Auciello said:
>
>> SA> Hello, I am a long time user and appreciator of emacs and I am SA>
>> SA> interested in contributing to it. [...]
>
>> The bug tracker is here:
>>
>> http://debbugs.gnu.org/cgi/pkgreport.cgi?package=emacs
>
> Lars Ingebrigtsen wrote a quick guide, "Welcome, New Emacs Developers",
> after the Emacs code repository was converted to git, which might also
> be of interest:
>
> * http://lars.ingebrigtsen.no/2014/11/13/welcome-new-emacs-developers/
That's a good start, and you've got to draw a line someplace, but I
think a nice addition to the above would be: "what Emacs versions are
new contributions supposed to be compatible with," and "how to
compile/test your contributions."
I've embarrassed myself a few times recently, writing things that Worked
For Me, and not realizing that that wasn't enough.
Eric
next prev parent reply other threads:[~2015-02-21 11:28 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 2:36 Emacs development Sam Auciello
2015-02-21 3:52 ` Alexis
2015-02-21 8:56 ` Eli Zaretskii
2015-02-21 10:07 ` Adam Sjøgren
2015-02-21 11:28 ` Eric Abrahamsen [this message]
2015-02-21 11:44 ` Eli Zaretskii
2015-02-21 12:24 ` Thien-Thi Nguyen
2015-02-21 12:27 ` Eli Zaretskii
2015-02-21 14:22 ` Thien-Thi Nguyen
2015-02-21 18:43 ` Eli Zaretskii
2015-02-22 17:17 ` Thien-Thi Nguyen
2015-02-21 12:45 ` Eric Abrahamsen
2015-02-24 10:58 ` Filipp Gunbin
-- strict thread matches above, loose matches on Subject: below --
2021-08-21 5:07 Jean-Christophe Helary
2021-08-21 6:46 ` Eli Zaretskii
2021-08-21 7:08 ` Jean-Christophe Helary
2021-08-21 7:16 ` Tassilo Horn
2021-08-21 7:50 ` Jean-Christophe Helary
2021-08-21 7:54 ` Tassilo Horn
2021-08-21 8:12 ` Eli Zaretskii
2021-08-21 13:51 ` Arthur Miller
2021-08-21 8:08 ` Stephen Berman
2021-08-21 12:05 ` Konstantin Kharlamov
2021-08-21 12:28 ` Jean-Christophe Helary
2021-08-21 14:08 ` Tim Cross
2021-08-21 15:00 ` Jean-Christophe Helary
2021-08-21 23:09 ` Tim Cross
2021-08-22 1:26 ` Jean-Christophe Helary
2021-08-22 2:25 ` Tim Cross
2021-08-22 2:15 ` Arthur Miller
2021-08-22 2:48 ` Tim Cross
2021-08-22 7:47 ` Arthur Miller
2021-08-22 8:11 ` Tim Cross
2021-08-22 13:54 ` T.V Raman
2021-08-22 16:04 ` Eric Abrahamsen
2021-08-22 16:19 ` Jean-Christophe Helary
2021-08-22 16:23 ` Eric Abrahamsen
2021-08-22 16:25 ` Arthur Miller
2021-08-22 16:43 ` Jean-Christophe Helary
2021-08-22 16:29 ` Arthur Miller
2021-08-22 17:08 ` T.V Raman
2021-08-22 17:44 ` Arthur Miller
2021-08-22 18:34 ` Stephen Berman
2021-08-22 23:12 ` Arthur Miller
2021-08-23 9:17 ` Arthur Miller
2021-08-22 14:41 ` Arthur Miller
2021-08-21 14:07 ` Arthur Miller
2021-08-21 8:10 ` Eli Zaretskii
2021-08-21 8:36 ` Alfred M. Szmidt
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=87oaon7bbx.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).