From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Emacs development
Date: Sat, 21 Feb 2015 20:43:50 +0200 [thread overview]
Message-ID: <83d253cdg9.fsf@gnu.org> (raw)
In-Reply-To: <87mw47gx9u.fsf@zigzag.favinet>
> From: Thien-Thi Nguyen <ttn@gnu.org>
> Date: Sat, 21 Feb 2015 15:22:05 +0100
>
> I'm not really sure I understand what these relationships
> are, or why are they important.
>
> Me too (re relationships), which is why it behooves those
> involved to state them explicitly (if possible).
There are many issues that might or might not be related to Emacs; we
don't normally describe them just because they might.
You could help understanding how these are related, by posting
questions that might bother newcomers, for which there are no ready
answers in the available documentation.
> I think it is related in that a newcomer's contributions may
> belong better in one repo or another, or even apart from Emacs
> (e.g., posted to gnu-emacs-sources only), due to relationships
> and expectations.
We only have one repository these days.
next prev parent reply other threads:[~2015-02-21 18:43 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
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 [this message]
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=83d253cdg9.fsf@gnu.org \
--to=eliz@gnu.org \
--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).