search for: vaildation

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

On Nov 10, 2008, at 12:59 PM, David Greene wrote: > I've written up a detailed proposal and attached it to this message. Yeah, mirrors in many ways something I've thought about for a while now. Roughly, cron (or while :; do) testers that figure out quality and create tags when that quality is met. Release branching can then just happen from the `prerelease' tag, and largely

Hello Ben, You can find below my results; there is a slight over-representation of 1st gen Tesla cards, but… that’s what I have. :-D No regressions observed, apart from: * screen rotation on G80, MCP79 * resuming on G86 I’ll retest those cards with your linux-4.10 branch but without the atomic + DP serie. Pierre Tested: linux-4.10 (HEAD at b27add13f "drm/nouveau/fifo/gf100-: protect

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 will not work for me. Don't know if that is > related. I am a UNIX admin and my Windows knowledge is limited. > -----Original Message----- > From: Dan.Boskovich@...

...ot reachable from master via the history graph, you know you missed moving some release fixes into master. Part of release validation then simply does "git branch --contains <release>" and checks that "master" is in the output. There are various tools to attempt the same vaildation when cherry-picking commits from master to release, but they rely on metadata on the cherry-picked commit (like the commit message with cherry-pick -x) and are thus somewhat fragile. I don't know of any tools that verify that fixes made on master make it to the release branch though I'm su...

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

...a] Re: Winbindd question/problem 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 will not work for me. Don't know if that is > related. I am a UNIX admin and my Windows knowledge is limited. > -----Original Message----- > From: Dan.Boskovich@...