Displaying 20 results from an estimated 86 matches for "unwelcom".
Did you mean:
unwelcome
2015 Apr 02
8
[CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64
It's not just the name of the ISO file. c.f. the VERSION_ID variable in
/etc/os-release
On Thu, Apr 2, 2015 at 10:52 AM, Always Learning <centos at u64.u22.net> wrote:
>
> On Wed, 2015-04-01 at 22:54 -0700, John R Pierce wrote:
>
> > you guys sure get your panties in a bunch over something as silly as the
> > iso file name.
>
> You may wear them, many of us
2015 Aug 03
1
unwelcome gthumb slideshow
I have a gif image in a folder.
Whenever I have gthumb display it or a copy of it,
gthumb goes into slideshow mode.
Usually I can stop the show.
It will not stop before going to the next image.
but I only have a slideshow period to look at the troublemaker.
If the troublemaker is last in the directory,
I cannot stop the show without stopping gthumb.
How do I make gthumb stop going into slideshow
2015 Apr 02
0
[CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64
On 04/02/2015 03:55 PM, Always Learning wrote:
> Is there a commercial motive for this 'unwelcome by most' change ?
Do you have data to prove that it is unwelcome by most? It is unwelcome
by you and a few others I've seen comment; what percentage of the list's
subscribers do you suppose that might be? (It is neither welcome nor
unwelcome by me, as I've said before.)
Feed...
2015 Apr 02
1
[CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64
On Thu, Apr 2, 2015 at 4:12 PM, Lamar Owen <lowen at pari.edu> wrote:
> On 04/02/2015 03:55 PM, Always Learning wrote:
>
>> Is there a commercial motive for this 'unwelcome by most' change ?
>>
>
> Do you have data to prove that it is unwelcome by most? It is unwelcome
> by you and a few others I've seen comment; what percentage of the list's
> subscribers do you suppose that might be? (It is neither welcome nor
> unwelcome by me, a...
2015 Oct 20
2
RFC: Second draft of an LLVM Community Code of Conduct
...everything after the second sentence seems
pretty unrelated. E.g. one of the examples is "Posting (or threatening to
post) other people's personally identifying information ("doxing")." - how
does that fall under anything involving "be careful"? Similarly for "Unwelcome
sexual attention." in what way does that involve "the words that you
choose"; is there a choice of words that makes "Unwelcome sexual
attention." any more or less acceptable? Same is true for " Repeated
harassment of others.".
Was there a typo and "Be kind...
2015 Apr 02
1
[CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64
On Thu, 2015-04-02 at 16:12 -0400, Lamar Owen wrote:
> On 04/02/2015 03:55 PM, Always Learning wrote:
> > Is there a commercial motive for this 'unwelcome by most' change ?
>
> Do you have data to prove that it is unwelcome by most?
Although most people in the world will privately complain the vast
majority do not complain in public. Where is your contrary evidence
that this non-beneficial and illogical change is welcome by the majority...
2018 Oct 22
5
[fdo] Code of Conduct questions
Hi,
I've cross-posted this to freedesktop@, as the xdg@ list is only used
for actual specification development.
On Mon, 22 Oct 2018 at 00:36, Jacob Lifshay <programmerjake at gmail.com> wrote:
> Hi, we were thinking of asking if freedesktop would host Kazan (https://github.com/kazan-3d/kazan) for us, however some of our community members have objections with how freedesktop's
2018 Nov 30
8
[PATCH RFC 00/15] Zero ****s, hugload of hugs <3
On Fri, 30 Nov 2018, Kees Cook wrote:
>On Fri, Nov 30, 2018 at 11:27 AM Jarkko Sakkinen
><jarkko.sakkinen at linux.intel.com> wrote:
>>
>> In order to comply with the CoC, replace **** with a hug.
I hope this is some kind of joke. How would anyone get offended by reading
technical comments? This is all beyond me...
Thanks,
Davidlohr
2014 Feb 18
2
[LLVMdev] asan coverage
On Feb 17, 2014, at 5:13 AM, Kostya Serebryany <kcc at google.com> wrote:
> Then my question: will there be any objection if I disentangle AsanCoverage from ASan and make it a separate LLVM phase with the proper clang driver support?
> Or it will be an unwelcome competition with the planned clang coverage?
I don’t view it as a competition, but assuming that we both succeed in our plans, LLVM would then end up with two very similar solutions for code coverage. Does it really make sense to have two?
2017 Sep 27
2
disturbed legend in ggplot2
Dear friends - below is a subset of a much larger material showing two
ways of generating two "lines". The intention is to have the colour
reflect a variable, pH, but the legend is disturbed. The little part
marked "3" above the colour scale is unwelcome. Why did it appear? How
could I avoid it?
I'm on Windows 7, R version 3.4.1 (2017-06-30) -- "Single Candle"
All best wishes
Troels Ring
Aalborg, Denmark
library(ggplot2)
DF1 <-
structure(list(P = c(0, 0.00222222222222222, 0.00444444444444444,
0.00666666666666667, 0.0088888888...
2015 Feb 13
1
Thread moderation and list etiquette (Reference - Another Fedora Decision)
...ith such intensity. This situation
A large part of this is that some of the regular people are now using
the list as a way to socialise and contribute 'me too' or 'yes/no' sort
of comments that dont really have much relevance to the real thread. All
of this not only makes the list unwelcoming to new users, it also
dramatically drops the quality of conversation.
If moderating is the only way to restore sanity and keep things
productive for the folks bringing through conversations then so be it,
we will start putting individual accounts on moderation.
--
Karanbir Singh
+44-207-09993...
1998 Mar 09
1
bug in menu, readline
Neither do_menu nor do_readln (in src/main/scan.c) call the function
InitConsoleGetchar. They need to do this to reset ConsolePrompt. If you
use "scan" to read in data from the terminal, then ConsolePrompt is set
to "n:" for some integer n and this prompt makes an unwelcome appearance
when you use the "menu" or "readline" functions.
Incidentally, could we have a "title" argument and a dummy "graphics"
argument for menu? This if for S-PLUS compatibility, if I may dare to
raise the topic.
Martyn
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-....
2012 May 25
1
klibc issues on armhf (not Debian/armel)
...ures,
cf. http://www.zytor.com/pipermail/klibc/2012-May/003277.html and
armhf is being one of them, when using klibc to compile mksh-static
with it.
I can look into it (asked zumbi for build-deps in a sid chroot on
harris already), but not 100% sure I?ll find it, so more eyes on
klibc would not be unwelcome ;-)
maks, does klibc on armel build thumb or not, and does it differ
from armhf in more than optimisation flags? (Does klcc use the
same flags as klibc itself was built with?)
Thanks,
//mirabilos
--
16:47??mika:#grml? .oO(mira ist einfach gut....) 23:22??mikap:#grml?
mirabilos: und dein bo...
2006 Nov 17
0
[LLVMdev] 1.9 Prerelease Available for Testing
...uot;llvm". Shouldn't
> > that be llvm-1.9?
>
> We have always labeled the dir just llvm which is fine. If you build
> llvm it will know its version 1.9.
I think that's missing the point. Convention is the foo-4.2.tar unpacks
to a directory called foo-4.2. It's a unwelcome surprise when it
doesn't, e.g. unpacking foo-4.1.tar and foo-4.2.tar in the same
directory for comparision, or worse unpacking foo-4.1.tar alongside your
llvm work directory.
Sure, it can be worked around, but even the Linux kernel followed this
convention in the end. Please consider it for...
2006 Nov 17
1
[LLVMdev] 1.9 Prerelease Available for Testing
...t
>>> that be llvm-1.9?
>>
>> We have always labeled the dir just llvm which is fine. If you build
>> llvm it will know its version 1.9.
>
> I think that's missing the point. Convention is the foo-4.2.tar unpacks
> to a directory called foo-4.2. It's a unwelcome surprise when it
> doesn't, e.g. unpacking foo-4.1.tar and foo-4.2.tar in the same
> directory for comparision, or worse unpacking foo-4.1.tar alongside your
> llvm work directory.
No its not. While this may be convention for other projects it has not
been for llvm. Therefore, peopl...
2016 Dec 05
2
LMTP delivery honours .forward by default?
On 2016-12-04 23:18, Steffen Kaiser wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Fri, 2 Dec 2016, MRob wrote:
>
>> I was under the impression that Dovecot does not look at .forward by
>> default, since of course, Sieve is where that kind of logic should go.
>> However, I'm seeing a .forward file being honoured by the LMTP
>>
2008 Sep 19
2
Specific SIP answers on incoming calls?
Hi,
when I still had ISDN, I was using Hangup(causecode) to send e.g. "Wrong
number" to unwelcome callers.
Meanwhile, I am only using SIP providers (no PSTN lines any more) and I
would like to do similar, i.e. send specific SIP headers. Besides "wrong
number", I would especially like to send 302 temp moved with a specified
address to deflect certain calls.
Is there any way to send a...
2015 Apr 02
1
[CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64
...t;
> On Thu, 2015-04-02 at 13:08 -0500, Johnny Hughes wrote:
>
>> CentOS releases are NOT the same as EUS and have never been .. yet that
>> seems to be what people expect. We want there to be no doubt on this
>> issue.
>
> Is there a commercial motive for this 'unwelcome by most' change ?
>
> If Centos is the same as RHEL then RH can loose valuable sales income
> because customers, actual and potential, use free Centos. However if
> Centos version numbers are vastly different from RHEL version numbers
> and there is no reliable method of equatin...
2021 Feb 04
3
Challenging times in trying to access oracle Linux documentation
Good afternoon everyone, hope you all are well.
Apologies if this is considered unwelcome -- asking oracle question in
centos group -- but a lot of centos Vs oracle is going on here so hoping
this will not be shot down.
I am unable to access any of the oracle documentation I need, as it keeps
on asking for support identifier number, which, as far as I can tell, is
only available if I...
2014 Feb 18
2
[LLVMdev] asan coverage
...n Feb 17, 2014, at 5:13 AM, Kostya Serebryany <kcc at google.com> wrote:
>> > Then my question: will there be any objection if I disentangle
>> AsanCoverage from ASan and make it a separate LLVM phase with the proper
>> clang driver support?
>> > Or it will be an unwelcome competition with the planned clang coverage?
>>
>> I don’t view it as a competition, but assuming that we both succeed in
>> our plans, LLVM would then end up with two very similar solutions for code
>> coverage. Does it really make sense to have two?
>
>
> It depe...