similar to: [RFC] Case insensitive assembly directives for all targets

Hi Manoj, I tried a few other options myself: * function 'target' attribute - the list of extensions this supports isn't complete and it doesn't enable the ACLE macros needed for intrinsics * manually defining ACLE macros - this allows intrinsics and is additive but assumes that you're not relying on codegen to emit instructions. I don't think it helps the bug linked

>> Here's something I learned when working with the FreeNAS folks : >> ZFS can be configured to be case insensitive when >> you create the filesystem (NOTE - cannot be altered >> *after* the filesystem is created). >> zfs create -o casesensitivity=insensitive filesystem In this case, will ZFS preserve capitals in file and directory names if they are so created

Hi Manoj, Not too late at all, we have not got to that point of the work yet. Are there examples of this kind of build setup that are available publicly? I think I understand the problem but it'd help to see one in action. To see if there are any other Arm extensions that are already being added like this and whether those systems support GCC and how. Thanks, David Spickett.

Hi, I have created an addition to the regex plugin that allows case insensitive matching for title/class/name/role. To enable the case insentive matching, I chose to prepend an 'i' before the tag (ititle=, iclass=, ...). The patch is obviously attached ;-) Are there any objections against putting this code in? Regards, Danny -------------- next part -------------- A non-text attachment

We have an application that was build on a windows platform that expects a case insensitive file system. Is there a way to set one up in CentOS? NTFS should work, I think, but I feel uneasy using that under Linux. Russ

Hi everyone, recently I get crazy about this software, but I came across a little trouble, can you help me? Thank a lot. It seems that there's no corresponding item that I can do with it in winecfg. Since my version is 1.3.35, I can't find the configure file like "~/.wine/configure". So, what's the proper way to solve this problem? Thanks.

We're using sieve with LMTP. We want to have lda_mailbox_autocreate and lmtp_save_to_detail_mailbox. Is there a way to make the "detail" case-insensitive? If so I have not found it yet. I suppose we could lowercase the input string for the SQL userdb query, but that's not what is wanted. The idea being that if a user makes a mailbox called "Test" is that user+test

I am trying to do file transfers through tftpd under fedora and I need the server to be case insensitive. I could not find any way to achieve this! Manual is useless! As an example I need to transfer file "foo.ext" even if I request file "FOO.Ext" which now spits an error saying that it does not exists. How can I do that?

I am having trouble with a simple gallery search. I type in a segment of the address and i only seem to be getting results if I use the correct case. This is in my Gallery controller: def search @gallery = Gallery.find(:all, :include => :property, :conditions => "address LIKE ''%#{@params[:keywords]}%''") end On a different note: I am having

I have the following validation code, however it will allow variations in case. Like ''Admin'' and ''admiN'', etc validates_exclusion_of :login, :in => %w( admin ), :message => "is reserved for system accounts" how can I make this validation case insensitive? -- Posted via http://www.ruby-forum.com/.

On 03/10/2014 06:56 PM, Ralph Giles wrote: > On 2014-03-10 2:47 PM, Jonathan Lennox wrote: >> If I add --disable-asm to the build, it builds correctly. >> >> Does anyone have experience with Apple assembler directives to know >> what?s the best way to fix this? I assume the Perl script to generate >> the assembler file is going to need to be modified somehow. >

Windows usernames are case-insensitive and almost any Unicode character is allowed in a username. The user should be able to login with her username given in any case and not be refused. However, this opens up a security problem in terms of the sshd_config Match rules. The match rules for user and group names have to operate case-insensitive as well, otherwise the user can override her settings

On Thu, Feb 06, 2020 at 11:46:26AM -0800, Jordan Rupprecht via llvm-dev wrote: > > Where was this policy, which sounds like replicating their design > mistakes bug-for-bug, agreed upon and documented? > James responded already, but just to add my perspective: on the subject of > llvm vs gnu binutils compatibility, I've heard everything in the range from > "let's do

Hi, Im looking for a way so I can have case insensitive user names, is there a configuration directive for this option ? as all I can find is the below patch with should give me what im looking for .. http://www.dovecot.org/list/dovecot/2004-March/003078.html

Hi, I have mail box info at mydomain.com stored in MySQL db. But dovecot is allowing me to login as both INFO at MYDOMAIN.COM info at mydomain.com Shows two mail boxes. The small letter account is the one mail server really deliver all mails. Is there any way i can specify all login names are small letters, so that user always access real mail box ? Regards, Yujin

Hi, I'm wondering what issues / problems I might run into if I'm using samba 3 on linux with the IBM JFS filesystem installed to be case-insensitive. I've had no luck finding anyone who says they've tried it. I'm having trouble with a group of Windows based developers programming in Delphi (Pascal) and Foxpro who seem to have real problems keeping the case of filenames

On Wed, 20 Feb 2019 at 23:54, Corinna Vinschen <vinschen at redhat.com> wrote: > The previous revert enabled case-insensitive user names again. This > patch implements the case-insensitive user and group name matching. > To allow Unicode chars, implement the matcher using wchar_t chars in > Cygwin-specific code. Keep the generic code changes as small as possible. > Cygwin:

Why can I do this.... validates_uniqueness_of "username", :case_sensitive=>false .... but not this.... User.where "Xx", :case_sensitive=>false ? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

Hi, Compiling a simple function with the 3.0 SVN branch llc produces .s output containing cfi_startproc, cfi_endproc, cfi_def_cfa_offset that gcc refuses to compile (OS X 10.7 on X86-64) with the following error: test.s:6:Unknown pseudo-op: .cfi_startproc test.s:10:Unknown pseudo-op: .cfi_def_cfa_offset test.s:10:Rest of line ignored. 1st junk character valued 51 (3). test.s:38:Unknown

others have found this problem ? this possible bug can be used by user in that way that one password login can use 2 maildirs in filesystem effitively give them all space qoutas and lost of other goodies so to speak: foo at example.com with a password can login with fOO at example.com and fOo at example.com add more chars to get more mailbox :/ confirms ? i found the problem when i had