From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Federico Beffa <beffa@ieee.org>, Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 6/6] gnu: Add emacs-slime.
Date: Thu, 31 Dec 2015 10:55:29 +1000 [thread overview]
Message-ID: <56847D01.3010702@uq.edu.au> (raw)
In-Reply-To: <CAKrPhPNBb2FoSGNM9cPgQe2i=7RQcKJyx6gzPo+4QW+SFO0KvQ@mail.gmail.com>
Hi Federico,
I'm just idly clicking though emails and I note that the description
doesn't contain 2 spaces after the full stops - so not a proper review.
Do you know though, is there any way to get emacs to insert the extra
space in description strings and comments automatically (without it
messing things up of course). Perhaps we should modify the importers to
insert this automatically in the description field.
Thanks,
ben
next prev parent reply other threads:[~2015-12-31 0:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 17:33 [PATCH 6/6] gnu: Add emacs-slime Federico Beffa
2015-12-31 0:55 ` Ben Woodcroft [this message]
2015-12-31 9:12 ` Federico Beffa
2016-01-05 22:17 ` Ludovic Courtès
2016-01-09 10:30 ` Federico Beffa
2016-01-09 15:27 ` Alex Kost
2016-01-09 18:45 ` Ludovic Courtès
2015-12-31 9:52 ` Ricardo Wurmus
2015-12-31 23:52 ` Alex Kost
2016-01-01 8:25 ` Ricardo Wurmus
2016-01-01 8:35 ` Ben Woodcroft
2016-01-01 15:04 ` Ricardo Wurmus
2016-01-05 14:25 ` [PATCH] import: Move beautify description from cran to utils. (was Re: [PATCH 6/6] gnu: Add emacs-slime.) Ben Woodcroft
2016-01-10 21:17 ` Ludovic Courtès
2016-01-14 9:49 ` Ben Woodcroft
2016-01-14 10:31 ` Ricardo Wurmus
2016-01-14 10:53 ` Ben Woodcroft
2016-01-14 11:30 ` Ricardo Wurmus
2016-01-14 12:15 ` Ben Woodcroft
2016-01-17 1:00 ` [PATCH] import: Move beautify description from cran to utils Ben Woodcroft
2016-01-18 9:45 ` Ludovic Courtès
2016-01-20 22:13 ` Ben Woodcroft
2016-01-21 8:51 ` Ludovic Courtès
2015-12-31 10:17 ` [PATCH 6/6] gnu: Add emacs-slime Alex Kost
2015-12-31 10:32 ` Federico Beffa
2015-12-31 20:40 ` Alex Kost
2015-12-31 10:33 ` Alex Kost
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=56847D01.3010702@uq.edu.au \
--to=b.woodcroft@uq.edu.au \
--cc=beffa@ieee.org \
--cc=guix-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 external index
https://git.savannah.gnu.org/cgit/guix.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.