xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Don Slutz <dslutz@verizon.com>
To: xen-devel@lists.xen.org
Cc: Keir Fraser <keir@xen.org>, Don Slutz <dslutz@verizon.com>,
	Jan Beulich <JBeulich@suse.com>
Subject: [PATCH 0/1] MAINTAINERS: Should use --cc (cc:) to supporters.
Date: Mon, 11 Nov 2013 13:22:16 -0500	[thread overview]
Message-ID: <1384194137-3169-1-git-send-email-dslutz@terremark.com> (raw)

From: Don Slutz <dslutz@verizon.com>

Attempt to make MAINTAINERS internal documention better about CC:

Don Slutz (1):
  MAINTAINERS: Should use --cc (cc:) to supporters.

 MAINTAINERS | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

-- 
1.8.4

             reply	other threads:[~2013-11-11 18:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11 18:22 Don Slutz [this message]
2013-11-11 18:22 ` [PATCH 1/1] MAINTAINERS: Should use --cc (cc:) to supporters Don Slutz
2013-11-12  9:45   ` Jan Beulich

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=1384194137-3169-1-git-send-email-dslutz@terremark.com \
    --to=dslutz@verizon.com \
    --cc=JBeulich@suse.com \
    --cc=keir@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 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).