All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Mike Shuey <shuey@purdue.edu>
Cc: oleg.drokin@intel.com, devel@driverdev.osuosl.org,
	gregkh@linuxfoundation.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org, HPDD-discuss@ml01.01.org
Subject: Re: [PATCH v2 1/8] staging: lustre: code cleanup - variable declaration spacing Clean up spacing in
Date: Fri, 08 May 2015 12:20:09 +0000	[thread overview]
Message-ID: <20150508122009.GU14154@mwanda> (raw)
In-Reply-To: <1431086460-22455-9-git-send-email-shuey@purdue.edu>


Put a blank line after the subject in git or it all gets put into the
email subject.

regards,
dan carpenter


WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Mike Shuey <shuey@purdue.edu>
Cc: oleg.drokin@intel.com, devel@driverdev.osuosl.org,
	gregkh@linuxfoundation.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org, HPDD-discuss@ml01.01.org
Subject: Re: [PATCH v2 1/8] staging: lustre: code cleanup - variable declaration spacing Clean up spacing in some variable declarations, to be more consistent.
Date: Fri, 8 May 2015 15:20:09 +0300	[thread overview]
Message-ID: <20150508122009.GU14154@mwanda> (raw)
In-Reply-To: <1431086460-22455-9-git-send-email-shuey@purdue.edu>


Put a blank line after the subject in git or it all gets put into the
email subject.

regards,
dan carpenter


  parent reply	other threads:[~2015-05-08 12:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 12:00 [PATCH v2 1/8] staging: lustre: code cleanup - variable declaration spacing Clean up spacing in some Mike Shuey
2015-05-08 12:00 ` [PATCH v2 1/8] staging: lustre: code cleanup - variable declaration spacing Clean up spacing in some variable declarations, to be more consistent Mike Shuey
2015-05-08 12:00 ` [PATCH v2 2/8] staging: lustre: remove lnet_fini_locks (dead code) Mike Shuey
2015-05-08 12:00   ` Mike Shuey
2015-05-08 12:00 ` [PATCH v2 3/8] staging: lustre: code cleanup - variable declaration spacing Mike Shuey
2015-05-08 12:00   ` Mike Shuey
2015-05-08 12:00 ` [PATCH v2 4/8] staging: lustre: remove LNetSetAsync - dead code Mike Shuey
2015-05-08 12:00   ` Mike Shuey
2015-05-08 12:00 ` [PATCH v2 5/8] staging: lustre: lnet: lnet: code cleanup - variable declaration spacing Mike Shuey
2015-05-08 12:00   ` Mike Shuey
2015-05-08 12:00 ` [PATCH v2 6/8] staging: lustre: lnet: lnet: Module is LNet, not Portals Mike Shuey
2015-05-08 12:00   ` Mike Shuey
2015-05-08 12:00 ` [PATCH v2 7/8] staging: lustre: code cleanup - variable declaration cleanups Mike Shuey
2015-05-08 12:00   ` Mike Shuey
2015-05-08 12:01 ` [PATCH v2 8/8] staging: lustre: code cleanup - normalize whitespace Mike Shuey
2015-05-08 12:01   ` Mike Shuey
2015-05-08 12:11   ` Julia Lawall
2015-05-08 12:11     ` Julia Lawall
2015-05-08 12:28   ` Dan Carpenter
2015-05-08 12:28     ` Dan Carpenter
2015-05-08 12:20 ` Dan Carpenter [this message]
2015-05-08 12:20   ` [PATCH v2 1/8] staging: lustre: code cleanup - variable declaration spacing Clean up spacing in some variable declarations, to be more consistent Dan Carpenter

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=20150508122009.GU14154@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=HPDD-discuss@ml01.01.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg.drokin@intel.com \
    --cc=shuey@purdue.edu \
    /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 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.