all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Gemini Lasswell <gazally@runbox.com>
Cc: emacs-devel@gnu.org
Subject: Re: Backtrace mode
Date: Sat, 28 Jul 2018 19:28:58 +0300	[thread overview]
Message-ID: <83d0v7tjcl.fsf@gnu.org> (raw)
In-Reply-To: <871sboqvx1.fsf@runbox.com> (message from Gemini Lasswell on Fri,  27 Jul 2018 13:13:30 -0700)

> From: Gemini Lasswell <gazally@runbox.com>
> Date: Fri, 27 Jul 2018 13:13:30 -0700
> 
> I've finished everything I set out to add to Backtrace mode, and have
> pushed it to scratch/backtrace-mode. Documentation, NEWS and tests are
> all done, so please have a look at it and let me know if you find
> anything that should be fixed before I merge it.

Thanks.  A few minor nits regarding documentation:

 . The first line of each NEWS entry should ideally be a single
   sentence; all the following sentences should begin on the second
   line.
 . Leave 2 spaces between sentences.
 . The closing brace of a cross-reference should be followed by a
   period or a comma.
 . The last (5th) argument of a cross-reference should be the official
   title of the manual to which you point, as stated in the title
   page.
 . When making cross-references to the current file, there's no need
   to specify that file's name by using the 4-argument cross-reference
   form.



  parent reply	other threads:[~2018-07-28 16:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-27 20:13 Backtrace mode Gemini Lasswell
2018-07-27 20:36 ` John Wiegley
2018-07-28 16:28 ` Eli Zaretskii [this message]
2018-08-01 15:22   ` Gemini Lasswell
2018-08-01 20:58 ` Clément Pit-Claudel
2018-08-03 15:48   ` Gemini Lasswell
2018-08-01 21:07 ` Clément Pit-Claudel
2018-08-03 17:14   ` Gemini Lasswell
2018-08-03 18:03     ` Clément Pit-Claudel

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83d0v7tjcl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gazally@runbox.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.