search for: vaildate

Hello all, I was wondering if someone could give me a brief explanation of how :scope works. I believe I''ve seen it used with the validation helpers in the past. - Jim

...They wouldn't have to guess if it builds or not, they'd just know it should (given then definition of the tag). The prerelease tag could be comprised of the mips tag, the x86 tag, the llvm x86 tag, .... One could even include things like the freebsd world build and boot and self vaildate tag. Might take a few days to run, but, doing this to feed into a preleasse style tag might be nice. I don't know just how useful this would be.

...: 4.8.7 Fullscreen game: Portal (FAIL is: it is not working, but neither did it before.) G80: * Basic modesetting: OK * VT switching: OK * Changing rotation: REGRESSION (disp: ERROR 5 [INVALID_STATE] * Suspend: OK * Hotplugging: - * Fullscreen game: FAIL (fail ttm_validate, vaildate: -12) (different on 4.8.7, but still failing) G84: * Basic modesetting: OK * VT switching: OK * Changing rotation: OK * Suspend: FAIL (DRM: base-0: timeout) * Hotplugging: OK * Fullscreen game: OK G86: * Basic modesetting: OK * VT switching: OK * Changing rotation: OK...

Hey all, I've just pushed out the initial Nouveau support for $subject \o/ As the atomic modesetting transition is basically a rewrite of the KMS portion of the driver, I would be very grateful for any additional testing that people could provide (even as simple as just booting and making sure you get a display is valuable). There's a Linux tree at

Hi, is it possible to change the default error messages? for example from ... errors prohibited this ... from being saved to something else? thanks, trung -- Posted via http://www.ruby-forum.com/.

Forgot to CC this to the list, so I'm sending it again. Sorry for the inconvenience. > -----Original Message----- > From: Dan.Boskovich@piedmontng.com > I have not been able to make the new version work > without using the UNIX password file for vaildation as yet. > If you could > offer some advise or tips to get there I would appreciate it. FYI: The > getent command

Artem Dergachev via cfe-dev <cfe-dev at lists.llvm.org> writes: > If you're doing merge commits, you might lose linear history, but you > obtain another fancy invariant: every piece of work - i.e., every > patch, every merge conflict resolution - appears in the repository > exactly once, under a unique identifier, and the non-linear source > control history becomes an

Back during the LLVM developer's meeting, I talked with some of you about a proposal to "validate" llvm. Now that 2.4 is almost out the door, it seems a good time to start that discussion. I've written up a detailed proposal and attached it to this message. The goal is to ease LLVM use by third parties. We've got consideral experience with LLVM and the community

Excuse my ignorance (I'm not great with Git) but how would it differ for workflows of people who use a Git repository for local work but still use `svn up + patch + svn commit <list of files>` to actually land post CR or for NFC patches, while resolving conflicts during a pull into a local (non-trunk) branch manually, after the eventual full switch to GitHub? I'm aware that SVN

I will be out of the office: From: Monday, Dec. 23rd Through: Friday, Jan. 3rd I will return to the office on Monday, Jan. 6th I will only be checking email or voicemail. Once or twice during that time period. Members of the I.T. dept. will be able to contact me if there is a critical issue. Enjoy the time off over the holidays and Happy New Year! >>> samba 12/21/02 12:00