similar to: New git repository

Anyone else notice that changeset 5980[1] hosed several of the db adapters? Specifically: activerecord/lib/active_record/connection_adapters/frontbase_adapter.rb activerecord/lib/active_record/connection_adapters/mysql_adapter.rb activerecord/lib/active_record/connection_adapters/openbase_adapter.rb activerecord/lib/active_record/connection_adapters/oracle_adapter.rb Someone has already filed

Hi all, I am at a small organization that has been using Samba for authentication for a while now, and I have inherited our Samba setup from our previous administrator. The server is in disrepair software-wise and would really benefit from a good reinstall. The problem is that our Samba implementation is mission-critical, so we need to get it replicated to another machine which can handle the

On Apr 27, 2015, at 9:07 AM, Joerg Schilling <Joerg.Schilling at fokus.fraunhofer.de> wrote: > > Heirloom added support for uname -S and for some linux ulimit extensions but > then stopped working on the code after a few months Ah. I had no idea it was in a state of disrepair. >> I see that you already wrote up the differences between osh and bosh in an earlier post. Is

Hi all, I am currently attempting to play Red Alert 2 on my Ubuntu 11.10 installation under Wine. Now, Red Alert 2 will launch fine, as expected on a Windows machine. The most minor error is the campaign selection screen where it takes an "alt-tab" to respond. I'm not so worried about this error. However, when I enter a single player game (Skirmish or Campaign), whenever the game

Is this better off in the bugtracker? ****Summary:**** Allow windows to be shrunken to 'mindows' individually and have a mixed environment of scaled and full sized windows. Mindows would grow to full size on mouseover rather than being interacted with while small and would be re-positionable. I'd love to have the time and ability to contribute more to this idea, but I can't see

Whamcloud and EMC are jointly investigating how to be able to contribute the Lustre client code into the upstream Linux kernel. As a prerequisite to this, EMC is working to clean up the Lustre client code to better match the kernel coding style, and one of the anticipated major obstacles to upstream kernel submission is the heavy use of code abstraction via libcfs for portability to other

Whamcloud and EMC are jointly investigating how to be able to contribute the Lustre client code into the upstream Linux kernel. As a prerequisite to this, EMC is working to clean up the Lustre client code to better match the kernel coding style, and one of the anticipated major obstacles to upstream kernel submission is the heavy use of code abstraction via libcfs for portability to other

I previously <https://groups.google.com/g/llvm-dev/c/u07o3QREVUg/> proposed contributing Bazel build files to the LLVM monorepo, supported *only* by interested community members and not to interfere with or affect the existing CMake configuration. As part of that conversation, it became clear that the LLVM policies for more "peripheral" components were not clearly documented. We

At 09:10 AM 9/17/2001 -0600, you wrote: >That's what logs are for. This is not a public log. Things are not >tracked over time. The information is only valid for a 'ttl' period. I'm just going to let this topic about listener counts lie.. I think enough people besides myself have stepped up in favor of it, and you have your reasons for not wanting to have it. It's

> It may be meaningless to most listeners, but having it tracked (and > public-domain) is valuable to admins and marketing types alike, if your > goals lean that way. That's what logs are for. This is not a public log. Things are not tracked over time. The information is only valid for a 'ttl' period. >Froma marketing angle, you might even argue the other way, that

In hopes of improving the quality, coverage, and currency of the Lustre User Manual, I''m putting out a call to the Lustre community for contributors to this important resource. The user manual is especially important for new users to Lustre, but has fallen into some disrepair now that there is no longer a dedicated documentation writer for it. As well, there are many sections of the

In hopes of improving the quality, coverage, and currency of the Lustre User Manual, I''m putting out a call to the Lustre community for contributors to this important resource. The user manual is especially important for new users to Lustre, but has fallen into some disrepair now that there is no longer a dedicated documentation writer for it. As well, there are many sections of the

Ok, that makes sense. I don't see this as a good enough argument to remove backslash support though. For problems like the clang_cc1 substitution mistakes, it would be much better to just improve the substitution support so that those cause immediate test failures. I would definitely support a move to make lit's substitution machinery more strict. For problems like your first search, I

Warren Young <wyml at etr-usa.com> wrote: > On Apr 27, 2015, at 4:38 AM, Joerg Schilling <Joerg.Schilling at fokus.fraunhofer.de> wrote: > > > > This is the SVr4 Bourne Shell, so you need to take into account what has been > > added with Svr4: > > Is there any difference between your osh and the Heirloom Bourne Shell? > >

On 11/16/20 10:01 PM, Geoffrey Martin-Noble via llvm-dev wrote: > I previously <https://groups.google.com/g/llvm-dev/c/u07o3QREVUg/ > > proposed contributing Bazel build files to the LLVM monorepo, > supported *only* by interested community members and not to interfere > with or affect the existing CMake configuration. As part of that > conversation, it became clear that

On 08/12/2013 16:43, Daniel Dunbar wrote: > > With one-to-one mapping, it becomes possible to use simple tools > like grep to validate common mistakes like %clang / %clang_cc1 > mixups, a missing -o flag and so on. > > Right now there's no obvious way to do those checks and we've > ended up without an easy way to lint for broken tests as a result.

So I've been doing some research and thinking here and there about what a _good_ directory service for icecast would be like. I'd appreciate some feedback and some discussion on this topic, before I start putting a lot of effort into developing it. First off, I think getting rid of # of listeners is a must. It just creates a self-fulfilling prophecy and encourages cheating. I think the