unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: Re: [PATCH 1/2] STYLE: document some rules about variable declarations
Date: Fri, 04 Mar 2016 20:49:01 -0400	[thread overview]
Message-ID: <871t7pvjeq.fsf@zancas.localnet> (raw)
In-Reply-To: <1455383479-9946-1-git-send-email-david@tethera.net>

David Bremner <david@tethera.net> writes:

> No-one seemed opposed to C99 style loop variable declarations. The
> requirement to declare variables at the top of blocks is maybe a little
> more contested, but I believe it reflects the status quo.

pushed both of these style guide updates

      parent reply	other threads:[~2016-03-05  0:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-13 17:11 [PATCH 1/2] STYLE: document some rules about variable declarations David Bremner
2016-02-13 17:11 ` [PATCH 2/2] STYLE: suggest long names David Bremner
2016-03-05  0:49 ` David Bremner [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://notmuchmail.org/

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

  git send-email \
    --in-reply-to=871t7pvjeq.fsf@zancas.localnet \
    --to=david@tethera.net \
    --cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).