From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [Patch 1/3] ocfs2-tools: Resolve rpmlint warnings in init scripts
Date: Tue, 25 Nov 2008 09:05:52 -0800 [thread overview]
Message-ID: <20081125170552.GB7479@mail.oracle.com> (raw)
In-Reply-To: <26ef5e70811250035p66a34458kf5ebd0b8d77a594f@mail.gmail.com>
On Tue, Nov 25, 2008 at 09:35:11AM +0100, Andrew Beekhof wrote:
> On Mon, Nov 24, 2008 at 23:30, Joel Becker <Joel.Becker@oracle.com> wrote:
> > On Mon, Nov 24, 2008 at 02:19:40PM -0800, Joel Becker wrote:
> >> rpmlint is wrong here, as it is tracking a SuSE-only behavior.
> >> At least, I can't find a RHEL system that behaves different from LSB.
> >
> > Actually, rpmlint is always wrong. An empty -Stop line is valid
> > on sles11 as well - it just means "the same as -Start".
>
> Ok, just ignore the this patch then.
> I've no personal attachment to them... its just something that the
> SUSE build system threw up and I wanted to be a good OSS citizen by
> submitting it upstream :-)
Did you see the other part, where I stated we should have
"Required-Stop" match "Required-Stop"? That's the correct change -
valid for LSB and for SLES11.
Joel
--
Life's Little Instruction Book #197
"Don't forget, a person's greatest emotional need is to
feel appreciated."
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
prev parent reply other threads:[~2008-11-25 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 10:18 [Ocfs2-devel] [Patch 1/3] ocfs2-tools: Resolve rpmlint warnings in init scripts Andrew Beekhof
2008-11-18 23:03 ` Joel Becker
2008-11-19 8:02 ` Andrew Beekhof
2008-11-24 22:19 ` Joel Becker
2008-11-24 22:30 ` Joel Becker
2008-11-25 8:35 ` Andrew Beekhof
2008-11-25 17:05 ` Joel Becker [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=20081125170552.GB7479@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=ocfs2-devel@oss.oracle.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.