All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] XML SDP Record Registration
Date: Thu, 23 Nov 2006 05:46:55 +0100	[thread overview]
Message-ID: <1164257215.4847.6.camel@localhost> (raw)
In-Reply-To: <200611231051.18032.denis.kenzior@trolltech.com>

Hi Denis,

> Oof, ouch.
> 
> In my defense, I followed the advice given in Linux CodingStyle document.  
> Most of the indentation issues you had a problem with was due to me using 
> 'indent' with the suggested options.
> 
> In the future I will happily follow the code style conventions you outline.  
> However, given that this is my first serious submission I cannot be expected 
> to 'guess' the conventions if they are not written down, especially since 
> these are not outlined in the Linux CodingStyle document.  

I simply have to keep the coding style unique for the whole project,
because otherwise patching will become a nightmare. We actually follow
the Linux kernel coding style and the best documentation is the paper
from Greg KH a couple of years ago. I linked the paper and his talk from
this page:

http://www.bluez.org/development.html

And one small piece of advise. Don't use indent. Nothing good comes out
of it. Following the kernel coding style also implies to rethink the
usage of goto and some other constructs where universities tried to tell
you that these are bad. However this is a learning process and when you
submit more and more patch you will definitely get a feel for it.

> Since it seems that BlueZ has further conventions that developers should be 
> following, which are not outlined in the Linux Coding Style documents, I 
> suggest that you include them on the Coding Style section of the Development 
> page of bluez.org to avoid such problems in the future :)

I should write something about the extra conventions, but to my shame, I
am too lazy.

Regards

Marcel



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2006-11-23  4:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21  5:04 [Bluez-devel] [PATCH] XML SDP Record Registration Denis KENZIOR
2006-11-21  7:41 ` Marcel Holtmann
2006-11-21 11:47   ` Marcel Holtmann
2006-11-21 23:59   ` Denis KENZIOR
2006-11-22  6:24     ` Marcel Holtmann
2006-11-23  0:51       ` Denis KENZIOR
2006-11-23  4:46         ` Marcel Holtmann [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=1164257215.4847.6.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.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.