From: Joshua Wright <jwright@hasborg.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Picky about coding style
Date: Thu, 25 Aug 2005 15:46:10 -0400 [thread overview]
Message-ID: <430E2002.2060309@hasborg.com> (raw)
In-Reply-To: <1124997684.8019.76.camel@pegasus>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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?
Thanks,
- -Josh
- --
- -Joshua Wright
jwright@hasborg.com
2005-2006 pgpkey: http://802.11ninja.net/pgpkey.htm
fingerprint: F00E 7A42 8375 0C55 964F E5A4 4D2F 22F6 3658 A4BF
Today I stumbled across the world's largest hotspot. The SSID is "linksys".
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDDiABTS8i9jZYpL8RAswwAKCxavrFA1OkutWuEaO3oG9zbDgPEQCcC6mY
OhwJfaVZkmDv/ge2nIJLgpI=
=zsw5
-----END PGP SIGNATURE-----
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-08-25 19:46 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 ` Joshua Wright [this message]
2005-08-25 19:53 ` [Bluez-devel] Picky about coding style Marcel Holtmann
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=430E2002.2060309@hasborg.com \
--to=jwright@hasborg.com \
--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.