From: Dan Carpenter <dan.carpenter@oracle.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Pranjal <bhor.pranjal@gmail.com>,
devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] staging: wlan-ng: Fixed block comment coding style
Date: Tue, 12 Jan 2016 14:11:28 +0300 [thread overview]
Message-ID: <20160112111127.GA4764@mwanda> (raw)
In-Reply-To: <20160111082116.GA8070@sudip-pc>
Weird... It applies with patch but not with git am.
Read the first paragraph of Documentation/email-clients.txt
`cat raw_email.txt | git am`
regards,
dan carpenter
prev parent reply other threads:[~2016-01-12 11:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 18:59 [PATCH 1/6] staging: wlan-ng: Fixed block comment coding style Pranjal Bhor
2016-01-09 4:28 ` Sudip Mukherjee
2016-01-09 5:53 ` Pranjal
2016-01-11 8:21 ` Sudip Mukherjee
2016-01-12 11:11 ` Dan Carpenter [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160112111127.GA4764@mwanda \
--to=dan.carpenter@oracle.com \
--cc=bhor.pranjal@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
/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).