xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"Keir (Xen.org)" <keir@xen.org>
Subject: Re: [PATCH] Document the current coding style conventions.
Date: Mon, 19 Mar 2012 11:18:51 +0000	[thread overview]
Message-ID: <4F67161B.1010406@citrix.com> (raw)
In-Reply-To: <1331804051.26979.44.camel@zakaz.uk.xensource.com>

On 15/03/12 09:34, Ian Campbell wrote:
> On Wed, 2012-03-14 at 17:27 +0000, David Vrabel wrote:
>> From: David Vrabel <david.vrabel@citrix.com>
>>
>> Based on a version originally posted in 2007.
>> http://lists.xen.org/archives/html/xen-devel/2007-06/msg00070.html
>>
>> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
>> ---
>>  docs/misc/coding_style.txt |  100 ++++++++++++++++++++++++++++++++++++++++++++
> 
> Thanks for this!
> 
> I think this should be CODING_STYLE at the top level (in the vein of
> top-level COPYRIGHT + local overrides).

The way I think most people will discover this will be via the
submitting patch page on the wiki.  If this doc is in the top-level can
it be linked from the wiki?

> [snip useful intro text]

I've incorporated this, thanks.

David

  parent reply	other threads:[~2012-03-19 11:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 17:27 [PATCH] Document the current coding style conventions David Vrabel
2012-03-15  9:11 ` Jan Beulich
2012-03-15  9:34 ` Ian Campbell
2012-03-15 10:54   ` David Vrabel
2012-03-15 11:07     ` Ian Campbell
2012-03-19 11:18   ` David Vrabel [this message]
2012-03-19 11:23     ` Ian Campbell
2012-03-15 18:23 ` Dario Faggioli
2012-03-16  9:23   ` 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=4F67161B.1010406@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xensource.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).