From: aq <aquynh@gmail.com>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Stefan Berger <stefanb@us.ibm.com>
Subject: Re: [PATCH] 1 of 2: default ssid to 0
Date: Sun, 26 Jun 2005 19:07:40 +0900 [thread overview]
Message-ID: <9cde8bff0506260307a91e65e@mail.gmail.com> (raw)
In-Reply-To: <200506260324.27847.mark.williamson@cl.cam.ac.uk>
On 6/26/05, Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote:
> > i think it is very bad idea to have 2 coding styles for code in kernel
> > and out of kernel. because people work on all those code must always
> > remember to adjust the editor configuration, depend on the code in or
> > out of kernel, which is a nightmare :-(
>
> Yes, it's an extra thing to think about. It also means that code imported
> from Linux needs adjusting to fit with the Xen coding convention.
>
> OTOH, we don't just work with the Linux kernel any more, so there will be
> multiple coding conventions anyhow. I just set up emacs so I can type "M-x
> xen-c-mode" or "M-x linux-c-mode".
>
> > how about this simple guide?
> > - C code complies Linux kernel coding style
>
> I don't think this is likely to happen any time soon - it'd require patches to
> all of Xen and the tools :-( (and probably to some of the Linux code but
> that's arguably desirable)
>
yes, that is too bad. but at least if we have an official style, we
can enforce the rules *from now on*. the old code can be fix later (if
possible).
regards,
aq
next prev parent reply other threads:[~2005-06-26 10:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-25 18:29 [PATCH] 1 of 2: default ssid to 0 Stefan Berger
2005-06-26 0:21 ` Anthony Liguori
2005-06-26 1:39 ` aq
2005-06-26 1:45 ` aq
2005-06-26 1:49 ` Mark Williamson
2005-06-26 2:18 ` aq
2005-06-26 2:24 ` Mark Williamson
2005-06-26 10:07 ` aq [this message]
2005-06-26 16:10 ` Stefan Berger
2005-06-26 16:13 ` Keir Fraser
2005-06-26 19:05 ` Chris Wright
2005-06-27 18:10 ` Josh Triplett
-- strict thread matches above, loose matches on Subject: below --
2005-06-26 3:20 Reiner Sailer
2005-06-26 10:04 ` aq
2005-06-26 13:55 ` David Hopwood
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=9cde8bff0506260307a91e65e@mail.gmail.com \
--to=aquynh@gmail.com \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=stefanb@us.ibm.com \
--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 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.