From: Greg KH <greg@kroah.com>
To: "Allyn, Mark A" <mark.a.allyn@intel.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alan@linux.intel.com" <alan@linux.intel.com>,
"Johnson, Charles F" <charles.f.johnson@intel.com>
Subject: Re: Introduction to rar_register patch set of 5 patches
Date: Fri, 22 Jan 2010 12:35:45 -0800 [thread overview]
Message-ID: <20100122203545.GB15734@kroah.com> (raw)
In-Reply-To: <8A0E4C92AE2D6D40AF99653191DA323160F7A280D1@rrsmsx501.amr.corp.intel.com>
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Fri, Jan 22, 2010 at 12:59:50PM -0700, Allyn, Mark A wrote:
> Greg:
>
> Just to be clear; then only the overall description of RAR should be
> in the cover email?
Yes, consider that something that introduces the series, but will be
deleted and never seen again. The actual description needs to be in the
patches themselves, as that is what is going to be committed to the
tree, and that information will show up in the changelog for everyone to
look at for forever.
> Perhaps I over reacted to you earlier comment that each patch had too
> much, so I moved everything to the intro email.
>
> I will re-submit with the description of each patch in each patch, but
> I will still list the patches in the intro.
Sure, that's fine.
thanks,
greg k-h
prev parent reply other threads:[~2010-01-22 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 17:53 Introduction to rar_register patch set of 5 patches Mark Allyn
2010-01-22 18:23 ` Randy Dunlap
2010-01-22 18:33 ` Greg KH
2010-01-22 19:59 ` Allyn, Mark A
2010-01-22 20:35 ` Greg KH [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=20100122203545.GB15734@kroah.com \
--to=greg@kroah.com \
--cc=alan@linux.intel.com \
--cc=charles.f.johnson@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.a.allyn@intel.com \
--cc=rdunlap@xenotime.net \
/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.