From: Greg KH <greg@kroah.com>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: Greg KH <gregkh@suse.de>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'devel@driverdev.osuosl.org'" <devel@driverdev.osuosl.org>,
"'virtualization@lists.osdl.org'" <virtualization@lists.osdl.org>,
Hank Janssen <hjanssen@microsoft.com>
Subject: Re: [PATCH 1/1] Rename camel case variables in channel.c (updated again)
Date: Mon, 27 Sep 2010 18:25:40 -0700 [thread overview]
Message-ID: <20100928012540.GA5188@kroah.com> (raw)
In-Reply-To: <1FB5E1D5CA062146B38059374562DF7289F19F42@TK5EX14MBXC130.redmond.corp.microsoft.com>
On Mon, Sep 27, 2010 at 10:59:33PM +0000, Haiyang Zhang wrote:
> > From: Greg KH [mailto:greg@kroah.com]
> > Sent: Monday, September 27, 2010 3:32 PM
>
> > What's wrong with using 'git send-email' with your server? Have you
> > tried that? That shouldn't change the mime-type of the patch, and if
> > it
> > does, that would be grounds for a bug to be filed against such a server,
> > right?
>
> I have sent the patch again with git-send-email. Is the email format correct
> now?
I do not know, as I did not recieve any such emails :)
Care to check that the messages really did get sent?
thanks,
greg k-h
next prev parent reply other threads:[~2010-09-28 1:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 22:04 [PATCH 1/1] Rename camel case variables in channel.c (updated) Haiyang Zhang
2010-09-23 22:38 ` Joe Perches
2010-09-24 16:08 ` Haiyang Zhang
2010-09-24 16:08 ` Haiyang Zhang
2010-09-24 16:06 ` [PATCH 1/1] Rename camel case variables in channel.c (updated again) Haiyang Zhang
2010-09-24 17:29 ` Joe Perches
2010-09-27 1:19 ` Greg KH
2010-09-27 2:52 ` Haiyang Zhang
2010-09-27 6:10 ` Greg KH
2010-09-27 17:57 ` Haiyang Zhang
2010-09-27 19:32 ` Greg KH
2010-09-27 22:59 ` Haiyang Zhang
2010-09-28 1:25 ` Greg KH [this message]
2010-09-24 16:06 ` Haiyang Zhang
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=20100928012540.GA5188@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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 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.