--- Begin Message ---
|
Subject: |
Re: Why does OpenSuSE disabled the default of allowing multi-core use in Coreutils 'sort'?? |
|
Date: |
Wed, 12 Sep 2012 12:34:55 -0700 |
|
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.24) Gecko/20100228 Lightning/0.9 Thunderbird/2.0.0.24 Mnenhy/0.7.6.666 |
Philipp Thomas wrote:from the changelog (where you
could have looked yourself ...).
I need to be convinced that sort threading works on all platforms
openSUSE/SLES support in order to disable that patch.
---
I wasn't aware that openSUSE supported all platforms. However
the people who wrote sort regularly do support 'many' platforms --
far more than what openSuSE supports.
Do you regularly disable feature from upstream requiring someone else
to provide extra proof that they work? Did you have some reason
to suspect that their fixes didn't work? Did you submit a bug
report upstream on the issue? I could easily have missed it, but
don't recall seeing one. If you don't submit bug reports they won't
get fixed.
Too often, I see see patches going back 7-10 versions for bugs openSuSE
has fixed in various progs/utils that should have been passed back
upstream -- but it doesn't *appear* that they have been -- if they
had been, you wouldn't need so many custom patches at build time.
If you're
willing to help and got a nice sample work load to stress test sort
threading I'd try to turn that into a test for the coreutils-testsuite
package that I could then build and thus run on all the supported
platforms.
----
They worked through multiple iterations of this algorithm to
find a balance that worked and you just throw away their work without
question?
Do you have reason to believe they have buggy code by default?
I'll Cc' the coreutils bug-list on this and open a bug-report on this as
should have been done originally, and maybe your questions can be addressed.
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#12427: Why does OpenSuSE disabled the default of allowing multi-core use in Coreutils 'sort'?? |
|
Date: |
Wed, 12 Sep 2012 22:27:35 +0200 |
tags 12427 notabug
thanks
Linda Walsh wrote:
...
> Do you have reason to believe they have buggy code by default?
> I'll Cc' the coreutils bug-list on this and open a bug-report on this as
> should have been done originally, and maybe your questions can be addressed.
Hi Linda,
Do you realize that by merely sending a message to bug-coreutils,
you have created an entry in our bug-tracking software? Here it is:
http://bugs.gnu.org/12427
If you can describe what you think is a bug in upstream coreutils, we
welcome such reports, but when you are not sure (as your message implies),
please address your mail to the address@hidden mailing list instead.
That is a more general forum, e.g., for discussion, where each new thread
does not create a new bug-tracking issue that someone will end up having
to re-read, maybe mark as "notabug" and close some day.
In the future, if you open an issue, you're welcome (encouraged, even)
to close it yourself if/when you realize that the issue is not considered
a bug. To close bug DDDDD, just send an email to address@hidden
where DDDDD is your bug number. That will save others the time and
trouble of having to close it for you, leaving them more time to address
issues that *are* deemed to be bugs.
The entire set of bugs:
http://debbugs.gnu.org/coreutils
Here are some graphs:
http://debbugs.gnu.org/rrd/coreutils.html
I've gone ahead and closed this issue (via the Cc' above),
but if you have details on a bug, please start a new thread
here to create a new one.
--- End Message ---