public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Shubham Goyal <shubham@linux.vnet.ibm.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: LTP list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] Review Required: [Re: [PATCH] fix mail02, 03 fail due to different sender names]
Date: Mon, 28 Feb 2011 13:11:14 +0530	[thread overview]
Message-ID: <4D6B519A.4050906@linux.vnet.ibm.com> (raw)
In-Reply-To: <AANLkTimWfcBNogrCzdsamTDPQ2iW0ce7iuHxUhCAw6_C@mail.gmail.com>

Alright Garrett.., I can understand your concerns on quality standardization and consistency across multiple platforms.
But how do we conclude my below question for now?

@Caspar: Any comments from your side?

Thanks,
Shubham


> On Thu, Feb 24, 2011 at 10:31 AM, Shubham Goyal
> <shubham@linux.vnet.ibm.com>  wrote:
>> Alright Garrett..., so how should we take the patches in userland arena in
>> future (including this one from Caspar)?
>> I mean should they be reviewed and merged upstream? Do LSB currently
>> involved in maintaining them?
> (this is going to seem like a bit of a rant, so please bear with me...)
>
> I don't know if the LSB actually has a test suite, but they should
> really get into the business of producing a test suite, because the
> LSB is mocked (in some circles) for being an excuse for a standards
> committee.
>
> FreeBSD devs (for sure) and many Linux devs know that there isn't a
> lot of decision making that goes into making Linux consistent across
> all platforms. Someone needs to herd all of the cats together and
> provide a means of testing standardization for these things (again,
> LSB) because then the quality element will properly trickle down in
> the GNU/Linux community.
>
> Right now everything's too ad hoc and messy for anyone depending on
> behavior to actually depend on Linux to remain constant over an
> extended period of time. That's one reason why (apart from GPL
> licensing) that people stay away from Linux: it's consistently
> inconsistent.
>
> Thanks,
> -Garrett


------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2011-02-28  7:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-28 17:41 [LTP] [PATCH] fix mail02,03 fail due to different sender names Caspar Zhang
2011-02-11 15:45 ` Caspar Zhang
2011-02-14  7:43 ` [LTP] Review Required: [Re: [PATCH] fix mail02, 03 fail due to different sender names] Caspar Zhang
2011-02-22 19:15   ` Shubham Goyal
2011-02-22 21:08     ` Garrett Cooper
2011-02-24 18:31       ` Shubham Goyal
2011-02-24 18:37         ` Garrett Cooper
2011-02-28  7:41           ` Shubham Goyal [this message]
2011-02-28  7:43             ` Garrett Cooper
2011-02-28  7:55             ` Caspar Zhang

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=4D6B519A.4050906@linux.vnet.ibm.com \
    --to=shubham@linux.vnet.ibm.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=yanegomi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox