unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 37414@debbugs.gnu.org
Subject: bug#37414: 26.3; (emacs) `Contributing': no `etc/CONTRIBUTE'
Date: Mon, 16 Sep 2019 09:22:26 -0700 (PDT)	[thread overview]
Message-ID: <cce16e82-e04f-41d8-94e1-08a08b5d6ee8@default> (raw)
In-Reply-To: <<8336gwxos2.fsf@gnu.org>>

> You have an old manual, from an older Emacs version.

emacs -Q for Emacs 26.3 says this in `(emacs) Contributing':

  If you would like to make more extensive contributions, see the
  'CONTRIBUTE' file in the Emacs distribution for information on
  how to be an Emacs developer.

> > Where is a user on MS Windows supposed to find file `CONTRIBUTE'?
> 
> In the source tree, as the contents of that file has changed and makes
> no sense without access to the sources.

No idea what "the source tree" means here.  That node tells
users to look for file CONTRIBUTE "in the Emacs distribution".
Where is it in the Emacs distribution?

The same node also says:

  It is important to write your patch based on the current
  working version.

But there's no spec of what constitutes a "patch" - what
to include in it or what form it takes.  Nothing about the
form of a patch file, change log etc.  Is such info in the
missing (?) CONTRIBUTE file?  If not, where is it?





       reply	other threads:[~2019-09-16 16:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<93efd688-4a2f-46d1-bb8b-805cbe6b7ccd@default>
     [not found] ` <<8336gwxos2.fsf@gnu.org>
2019-09-16 16:22   ` Drew Adams [this message]
2019-09-16 16:42     ` bug#37414: 26.3; (emacs) `Contributing': no `etc/CONTRIBUTE' Eli Zaretskii
     [not found] <<<<93efd688-4a2f-46d1-bb8b-805cbe6b7ccd@default>
     [not found] ` <<<<8336gwxos2.fsf@gnu.org>
     [not found]   ` <<<cce16e82-e04f-41d8-94e1-08a08b5d6ee8@default>
     [not found]     ` <<<83v9tsw5tv.fsf@gnu.org>
     [not found]       ` <<5d48e5eb-59d7-44c6-972e-deba07847ba2@default>
     [not found]         ` <<83tv9cw2cn.fsf@gnu.org>
2019-09-16 18:24           ` Drew Adams
2020-10-18 12:16             ` Stefan Kangas
2021-09-25  1:38               ` Stefan Kangas
     [not found] <<<93efd688-4a2f-46d1-bb8b-805cbe6b7ccd@default>
     [not found] ` <<<8336gwxos2.fsf@gnu.org>
     [not found]   ` <<cce16e82-e04f-41d8-94e1-08a08b5d6ee8@default>
     [not found]     ` <<83v9tsw5tv.fsf@gnu.org>
2019-09-16 17:16       ` Drew Adams
2019-09-16 17:57         ` Eli Zaretskii
2019-09-15 22:13 Drew Adams
2019-09-15 22:18 ` Drew Adams
2019-09-16 15:07 ` Eli Zaretskii

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=cce16e82-e04f-41d8-94e1-08a08b5d6ee8@default \
    --to=drew.adams@oracle.com \
    --cc=37414@debbugs.gnu.org \
    --cc=eliz@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).