From: Don Slutz <dslutz@verizon.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>,
Don Slutz <dslutz@verizon.com>
Cc: Keir Fraser <keir@xen.org>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v2 1/2] xentrace: Add emacs local variables
Date: Tue, 01 Apr 2014 17:42:02 -0400 [thread overview]
Message-ID: <533B32AA.5030404@terremark.com> (raw)
In-Reply-To: <CAFLBxZZB3PW-DSzz4agDOJqwUGtnz1Ya2dr1HcreMegFCfD_nw@mail.gmail.com>
On 04/01/14 05:16, George Dunlap wrote:
> On Fri, Mar 28, 2014 at 4:56 PM, Don Slutz <dslutz@verizon.com> wrote:
>> This is per CODING_STYLE.
>>
>> Signed-off-by: Don Slutz <dslutz@verizon.com>
> Er, this change doesn't have anything to do with xentrace; it's a bit
> misleading to have that in the short description.
Ok. How about:
Add emacs local variables to all files changed.
-Don Slutz
> -George
next prev parent reply other threads:[~2014-04-01 21:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 16:56 [PATCH v2 0/2] xentrace: Add TRC_HVM_VCHIP (was xentrace: Add TRC_HW_VCHIP) Don Slutz
2014-03-28 16:56 ` [PATCH v2 1/2] xentrace: Add emacs local variables Don Slutz
2014-04-01 9:16 ` George Dunlap
2014-04-01 21:42 ` Don Slutz [this message]
2014-03-28 16:56 ` [PATCH v2 2/2] xentrace: Add TRC_HVM_VCHIP Don Slutz
2014-04-01 13:23 ` George Dunlap
2014-04-01 17:42 ` Don Slutz
2014-04-03 10:36 ` Tim Deegan
2014-04-01 13:06 ` [PATCH v2 0/2] xentrace: Add TRC_HVM_VCHIP (was xentrace: Add TRC_HW_VCHIP) George Dunlap
2014-04-01 15:18 ` Don Slutz
2014-04-01 16:01 ` George Dunlap
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=533B32AA.5030404@terremark.com \
--to=dslutz@verizon.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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.