From: John Wiegley <jwiegley@gmail.com>
To: Alex <agrambot@gmail.com>
Cc: Alan Mackenzie <acm@muc.de>, emacs-devel@gnu.org
Subject: Re: Should there be a k&r2 c-style?
Date: Sun, 25 Sep 2016 11:56:39 -0700 [thread overview]
Message-ID: <m2lgyfyfiw.fsf@newartisans.com> (raw)
In-Reply-To: <87bmzgonlk.fsf@gmail.com> (Alex's message of "Wed, 21 Sep 2016 17:11:03 -0600")
>>>>> "A" == Alex <agrambot@gmail.com> writes:
A> If it's acceptable, would you commit it for me?
Yes, I'd be happy to.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
prev parent reply other threads:[~2016-09-25 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 19:24 Should there be a k&r2 c-style? Alex
2016-09-09 19:35 ` John Wiegley
2016-09-09 20:08 ` Alex
2016-09-09 20:54 ` John Wiegley
2016-09-21 17:41 ` Alex
2016-09-21 20:12 ` John Wiegley
2016-09-21 23:11 ` Alex
2016-09-25 18:56 ` John Wiegley [this message]
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=m2lgyfyfiw.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=acm@muc.de \
--cc=agrambot@gmail.com \
--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).