From: Eric Sunshine <sunshine@sunshineco.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH] t3200 (branch): modernize style
Date: Wed, 20 Mar 2013 15:50:43 -0400 [thread overview]
Message-ID: <CAPig+cSAzCM893kunUO=FM5Qh0-+5YON1KfbG4rUiDjZ8CvV4w@mail.gmail.com> (raw)
In-Reply-To: <1363782612-19260-1-git-send-email-artagnon@gmail.com>
On Wed, Mar 20, 2013 at 8:30 AM, Ramkumar Ramachandra
<artagnon@gmail.com> wrote:
> Style is inconsistent throughout the file. Make the following
> changes:
>
> 1. Indent everything with tabs.
>
> 2. Put the opening quote (') for the test in the same line as
> test_expect_succcess, and the closing quote on a line by itself.
s/succcess/success/
next prev parent reply other threads:[~2013-03-20 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 12:30 [PATCH] t3200 (branch): modernize style Ramkumar Ramachandra
2013-03-20 19:50 ` Eric Sunshine [this message]
2013-03-20 19:57 ` Ramkumar Ramachandra
2013-03-20 20:43 ` Junio C Hamano
2013-03-20 21:34 ` Junio C Hamano
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='CAPig+cSAzCM893kunUO=FM5Qh0-+5YON1KfbG4rUiDjZ8CvV4w@mail.gmail.com' \
--to=sunshine@sunshineco.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.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.
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 NNTP newsgroup(s).