From: Jeffrey Layton <jtlayton@poochiereds.net>
To: raven@themaw.net
Cc: autofs@linux.kernel.org
Subject: Re: [PATCH] replicated mounts fix, also possible bug in beta2?
Date: Sun, 03 Apr 2005 06:11:55 -0400 [thread overview]
Message-ID: <424FC16B.4030006@poochiereds.net> (raw)
In-Reply-To: <Pine.LNX.4.62.0504031153230.8220@donald.themaw.net>
raven@themaw.net wrote:
>
> Thanks for that.
>
> As you probably realise adding this to the current beta is not a good
> idea as this needs to stabilise to go to release. Making a significant
> change like this at this time is a bad idea. So it's 4.1.5. At least
> your not alone, I have a couple of other patches.
>
> I'll have a look.
>
> One think I noticed is that there are places where there's a 4
> character indent. While that's present in other places in the code I
> prefer a straight 8 char tab for all indents. Long lines are really
> bad as well and we should try our best to keep them short. I try to
> keep lines to 80 chars (but often don't succeed).
>
> The usual thinking is that if the code needs to be indented to far it
> needs to be restructured.
>
> Anyway they're my goals.
Sounds good. I didn't expect this to go into 4.1.4 -- it's too big a
change for that, but if you could consider it for 4.1.5 that would be great.
I'll try to clean up the indenting and see if I shorten some of the
lines (maybe I'll take a stab at running it through "indent" first).
Most of the long lines are due to debug statements in the code, so some
of those can probably be removed once the code stabilizes a bit.
Thanks,
Jeff
next prev parent reply other threads:[~2005-04-03 10:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 11:55 [PATCH] replicated mounts fix, also possible bug in beta2? Jeff Layton
2005-04-02 16:53 ` raven
2005-04-02 19:31 ` Jeff Layton
2005-04-03 4:03 ` raven
2005-04-03 10:11 ` Jeffrey Layton [this message]
2005-04-04 2:19 ` Ian Kent
2005-04-08 14:21 ` Jeffrey Layton
2005-04-08 17:40 ` Jeff Moyer
2005-04-09 3:41 ` raven
2005-04-09 11:53 ` Jeff Layton
2005-04-09 3:30 ` raven
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=424FC16B.4030006@poochiereds.net \
--to=jtlayton@poochiereds.net \
--cc=autofs@linux.kernel.org \
--cc=raven@themaw.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.