From: David Bremner <david@tethera.net>
To: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: [PATCH] NEWS: consistent 2-space indentation in new content
Date: Thu, 22 Mar 2012 08:31:21 -0300 [thread overview]
Message-ID: <87ehskeut2.fsf@zancas.localnet> (raw)
In-Reply-To: <1332358349-12135-1-git-send-email-tomi.ollila@iki.fi>
On Wed, 21 Mar 2012 21:32:29 +0200, Tomi Ollila <tomi.ollila@iki.fi> wrote:
> Some 0.12 NEWS items descriptions were indented with 3 spaces whereas
> all other lines are indented with 2 spaces. Brought those
> escaped lines back in line with others.
That would be my fault.
Pushed.
d
prev parent reply other threads:[~2012-03-22 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 19:32 [PATCH] NEWS: consistent 2-space indentation in new content Tomi Ollila
2012-03-22 11:31 ` 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=87ehskeut2.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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).