All of lore.kernel.org
 help / color / mirror / Atom feed
From: Domen Puncer <domen@coderock.org>
To: "Edgar, Bob" <Bob.Edgar@commerzbankib.com>
Cc: "'Jesper Juhl'" <juhl-lkml@dif.dk>,
	"Steve French" <sfrench@us.ibm.com>,
	"Jörn Engel" <joern@wohnheim.fh-wedel.de>,
	"Luca Tettamanti" <kronos@kronoz.cjb.net>,
	samba-technical <samba-technical@lists.samba.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] whitespace cleanups for fs/cifs/file.c
Date: Mon, 7 Mar 2005 11:30:14 +0100	[thread overview]
Message-ID: <20050307103014.GD18117@nd47.coderock.org> (raw)
In-Reply-To: <9D248E1E43ABD411A9B600508BAF6E9B0C737269@xmx7fraib.fra.ib.commerzbank.com>

On 07/03/05 10:26 +0100, Edgar, Bob wrote:
> I lurk on the list and didn't comment last time but there is one aspect
> of this patch that I think is "bad" style. The function declaration should
> not be on the same line with the type. Why? Try to find the file where a
> function is defined instead of used. If you grep "^funcname" you'll find
> it quite simply. The same is true in YFE (mine being vi) /^funcname gets
> me there in one shot.

Does anybody actually use grep "^funcname"? cscope/ctags is the way.

> 
> This may not seem an important thing but when you are coming into a
> project cold and don't know how anything works or where it lives it
> can be very important. Consider trying to find where some common
> function from a library is defined in a project with sever 1000 files.

Again... cscope or ctags will make your life much easier here.

> 
> I now return you to your regularly scheduled programming.
> 
> bob
> 
> -----Original Message-----
> From:
> samba-technical-bounces+bob.edgar=commerzbankib.com@lists.samba.org
> [mailto:samba-technical-bounces+bob.edgar=commerzbankib.com@lists.samba.
> org]On Behalf Of Jesper Juhl
> Sent: Freitag, 4. März 2005 20:24
> To: Steve French
> Cc: Jörn Engel; Luca Tettamanti; samba-technical; Linux Kernel Mailing
> List; Domen Puncer
> Subject: [PATCH] whitespace cleanups for fs/cifs/file.c
...
> -int
> -cifs_open(struct inode *inode, struct file *file)
> +int cifs_open(struct inode *inode, struct file *file)
...

  parent reply	other threads:[~2005-03-07 10:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07  9:26 [PATCH] whitespace cleanups for fs/cifs/file.c Edgar, Bob
2005-03-07 10:28 ` Jörn Engel
2005-03-07 10:28 ` Andreas Dilger
2005-03-07 10:32   ` Jörn Engel
2005-03-08  3:33     ` Jesper Juhl
2005-03-08  3:31   ` Jesper Juhl
2005-03-07 10:30 ` Domen Puncer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-04 19:23 Jesper Juhl
2005-03-04 19:45 ` Christopher R. Hertel
2005-03-04 19:49   ` Jesper Juhl

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=20050307103014.GD18117@nd47.coderock.org \
    --to=domen@coderock.org \
    --cc=Bob.Edgar@commerzbankib.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=juhl-lkml@dif.dk \
    --cc=kronos@kronoz.cjb.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samba-technical@lists.samba.org \
    --cc=sfrench@us.ibm.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.