From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Picky about coding style
Date: Thu, 25 Aug 2005 21:53:19 +0200 [thread overview]
Message-ID: <1124999599.8019.77.camel@pegasus> (raw)
In-Reply-To: <430E2002.2060309@hasborg.com>
Hi Josh,
> While reading up on the Linux kernel coding style to satisfy patch
> requirements, I came the kernel scripts/Lindent script:
>
> mercury:/usr/src/linux/scripts $ cat Lindent
> #!/bin/sh
> indent -kr -i8 -ts8 -sob -l80 -ss -ncs "$@"
> mercury:/usr/src/linux/scripts $
>
> Is it safe to use this script to satisfy formatting requirements for
> patch submissions for BlueZ?
if you do it once, then yes, but in general you should use the correct
coding style from the start. Check Greg's OLS talk for details.
Regards
Marcel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-08-25 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 19:08 [Bluez-devel] An Introduction to Bluetooth programming in GNU/Linux Albert Huang
2005-08-25 19:21 ` Marcel Holtmann
2005-08-25 19:46 ` [Bluez-devel] Picky about coding style Joshua Wright
2005-08-25 19:53 ` 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=1124999599.8019.77.camel@pegasus \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox