From: Xue Fuqiao <xfq.free@gmail.com>
To: Ken Manheimer <ken.manheimer@gmail.com>
Cc: Glenn Morris <rgm@gnu.org>, Eli Zaretskii <eliz@gnu.org>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: master 89898fc: Repair pdbtrack so it follows transition from one remote file to another.
Date: Mon, 21 Sep 2015 07:01:00 +0800 [thread overview]
Message-ID: <CAAF+z6EnqkKwbQ8eZdT3za6pYjTYdxyjr9Q+K11REMx8zZ2dpw@mail.gmail.com> (raw)
In-Reply-To: <CAAT_zTEyPc1+4xmTBLzTMYqwAreQEQBFsEEgVrwaVZu6J2MKMQ@mail.gmail.com>
On Sun, Sep 20, 2015 at 11:59 PM, Ken Manheimer <ken.manheimer@gmail.com> wrote:
> Also, I have finally found the location of guidance for commit messages -
> CONTRIBUTORS in the source directory root. I had looked for guidance in
> http://www.emacswiki.org/emacs/GitForEmacsDevs - it would have be helpful if
> that prominently directed contributors to the CONTRIBUTORS file. Perhaps I'm
> just oblivious, but it seems like the various guidance resources are
> scattered enough that there is not an unmissable "garden path" to fill
> people in.
Perhaps you can edit that page and mention CONTRIBUTE (not CONTRIBUTORS,
sorry for the nitpick) in the page. Here are the URIs of CONTRIBUTE in
the current stable release and master:
* https://www.gnu.org/software/emacs/CONTRIBUTE
* http://git.savannah.gnu.org/cgit/emacs.git/plain/CONTRIBUTE
next prev parent reply other threads:[~2015-09-20 23:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-20 15:59 master 89898fc: Repair pdbtrack so it follows transition from one remote file to another Ken Manheimer
2015-09-20 17:06 ` Eli Zaretskii
2015-09-20 23:01 ` Xue Fuqiao [this message]
2015-09-22 4:25 ` Ken Manheimer
[not found] <20150920013701.15507.11501@vcs.savannah.gnu.org>
[not found] ` <E1ZdTYr-00042q-6b@vcs.savannah.gnu.org>
2015-09-20 10:44 ` Glenn Morris
2015-09-20 11:35 ` Glenn Morris
2015-09-20 12:40 ` 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=CAAF+z6EnqkKwbQ8eZdT3za6pYjTYdxyjr9Q+K11REMx8zZ2dpw@mail.gmail.com \
--to=xfq.free@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ken.manheimer@gmail.com \
--cc=rgm@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).