search for: reverted

..., and extract the change using svn diff or git diff to a patch file. Then use patch to apply it locally, using the '-R' flag for reverse, and fix any merge conflicts. If your tests run clean, update your source one last time just in case, then commit with a new message indicating that you reverted it with a note on why, etc... hth... don On Tue, Mar 26, 2019 at 12:08 AM Xing GUO via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: Hi folks, Several days ago, I made a bad change in llvm, and I reverted it using following command ``` $ svn merge -r...

...d is terrified of the implied effort of having to engage each author of a broken patch individually while being unable to ship or see what other breakage is coming in.  Admittedly, self serving perspective.  :) Philip p.s. Speaking personally, I actually *prefer* having a patch of mine simply reverted w/o discussion when there's a problem.  This way there's no expectation of timely response on my side, and if I happen to be out of office, or on vacation, I can get to it when I get back and have time.  I do expect to be *informed* of the revert of course. On 2/20/19 1:35 PM, Justin Bo...

Hi folks, Several days ago, I made a bad change in llvm, and I reverted it using following command ``` $ svn merge -r <bad change revision>:<previous revision> ``` However, this command seemed not working properly. I would like to know, what's the right way to revert a bad change. I notice that there are some reverting change with proper message, e.g. &...

This is kind of what I was getting at with my original email, so thank you for wording it better than I did. If we can agree that "contact the author first for internal bots" is better than "revert automatically, even for internal bots" (which may not be the case, I don't want to speak for others), then the problem becomes one of defining what an "internal bot"

...not, the next best thing is an email that was automatically sent to me (along with everyone else on the blamelist) from the buildbot with information about the failure. And then finally, I'll occasionally get a response to my commit message telling me that it's broken, and the patch may be reverted with information in the commit message explaining which bot was broken and providing a link to it. However, we have some buildbots on the public waterfall which are specifically configured not to send emails to people. In some cases it's because the bots are experimental, but there are a hand...

...not, the next best thing is an email that was automatically sent to me (along with everyone else on the blamelist) from the buildbot with information about the failure. And then finally, I'll occasionally get a response to my commit message telling me that it's broken, and the patch may be reverted with information in the commit message explaining which bot was broken and providing a link to it. However, we have some buildbots on the public waterfall which are specifically configured not to send emails to people. In some cases it's because the bots are experimental, but there are a hand...

Reid said: > I don't think whether a buildbot sends email should have anything to do > with whether we revert to green or not. Very often, developers commit > patches that cause regressions not caught by our buildbots. If the > regression is severe enough, then I think community members have the > right, and perhaps responsibility, to revert the change that caused it. > Our

I am trying to revert a commit, and the instructions here don't work as the revert support was removed from the git-llvm script last week when the migration happened. The instructions on the website still reference it however: https://llvm.org/docs/GettingStarted.html#reverting-a-change-when-using-git I am going to do it manually, but a script would be helpful for automating the commit

Can you explain how to revert for someone who is a 2 on a git scale of 0 to 10? At 9/22/2020 03:51 PM, Arthur Eubanks wrote: >Yes, push whatever is needed to fix the build if the fix is fairly simple (else revert and get an LGTM with the fix). > >Next time I'd recommend creating and pushing a revert first if you can't quickly figure out the issue.

This series reverts the in-kernel workarounds for inlining issues. The commit description of 77b0bf55bc67 mentioned "We also hope that GCC will eventually get fixed,..." Now, GCC provides a solution. https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html explains the new "asm inline" syntax. The performance issue will be eventually solved. [About Code cleanups] I know Nadam

This series reverts the in-kernel workarounds for inlining issues. The commit description of 77b0bf55bc67 mentioned "We also hope that GCC will eventually get fixed,..." Now, GCC provides a solution. https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html explains the new "asm inline" syntax. The performance issue will be eventually solved. [About Code cleanups] I know Nadam

...mbered list in > http://llvm.org/docs/DeveloperPolicy.html#code-reviews ? > > > > #. Sometimes patches get committed that need more discussion. > If a developer thinks that a patch would benefit from some more > review > and promptly communicates this, the patch should be reverted > (preferably > by the original author, unless they are unresponsive). > Developers often disagree, and erring on the side of the developer > asking for more review prevents any lingering disagreement over code > in > the tree. > > > "promptly" is there mostly...

Hi there, I''m running several VMs within Xen, and now I''m trying to create/revert snapshots of my VMs. Along with Xen and blktap2, another utility, vhd-util is also delivered, and according to its description, i guess I can use it to create/revert VM snapshots. To create a snapshot is actually easy, I just call |vhd-util snapshot -n aSnapShot.vhd -p theVMtoBackup.vhd | But

....rst as an item at the end of the numbered list in http://llvm.org/docs/DeveloperPolicy.html#code-reviews ? #. Sometimes patches get committed that need more discussion. If a developer thinks that a patch would benefit from some more review and promptly communicates this, the patch should be reverted (preferably by the original author, unless they are unresponsive). Developers often disagree, and erring on the side of the developer asking for more review prevents any lingering disagreement over code in the tree. "promptly" is there mostly to avoid suggesting a "necro...

Hi, I''m just trying out the possibilities of script.aculo.us / prototype having two problems... I have a draggable element with revert:false-property and two dropzones. (The draggables are in a <td> and the dropzones are <div>s if that is important.) 1. I want the draggable element to snap back to its original position when it gets dropped anywhere out of a dropzone. 2.

On 2019/9/5 ??9:59, Jason Gunthorpe wrote: > On Thu, Sep 05, 2019 at 08:27:34PM +0800, Jason Wang wrote: >> Hi: >> >> Per request from Michael and Jason, the metadata accelreation is >> reverted in this version and rework in next version. >> >> Please review. >> >> Thanks >> >> Jason Wang (2): >> Revert "vhost: access vq metadata through kernel virtual address" >> vhost: re-introducing metadata acceleration through kernel virt...

On 2019/9/5 ??9:59, Jason Gunthorpe wrote: > On Thu, Sep 05, 2019 at 08:27:34PM +0800, Jason Wang wrote: >> Hi: >> >> Per request from Michael and Jason, the metadata accelreation is >> reverted in this version and rework in next version. >> >> Please review. >> >> Thanks >> >> Jason Wang (2): >> Revert "vhost: access vq metadata through kernel virtual address" >> vhost: re-introducing metadata acceleration through kernel virt...

I am running Ubuntu Dapper Drake with Wine 9.9 - I tried to load Photoshop 4 with the following results: :~$ wine "/media/cdrom/photoshp/disk1/setup.exe" libGL warning: 3D driver returned no fbconfigs. libGL error: InitDriver failed libGL error: reverting to (slow) indirect rendering libGL warning: 3D driver returned no fbconfigs. libGL error: InitDriver failed libGL error: reverting to

...tions(+), 345 deletions(-) > create mode 100644 arch/x86/include/asm/alternative-common.h > delete mode 100644 arch/x86/kernel/macros.S I absolutely agree that this needs to be resolved in v4.20. So I did the 1-9 reverts manually myself as well, because I think the first commit should be reverted fully to get as close to the starting point as possible (we are late in the cycle) - and came to the attached interdiff between your series and mine. Does this approach look OK to you, or did I miss something? Thanks, Ingo =============> entry/calling.h | 2 - include/asm/ju...

> -----Original Message----- > From: linux-acpi-owner at vger.kernel.org <linux-acpi-owner at vger.kernel.org> On > Behalf Of Dave Airlie > Sent: Wednesday, August 14, 2019 5:48 PM > To: Karol Herbst > Cc: LKML; Linux ACPI; dri-devel; nouveau; Rafael J . Wysocki; Alex Hung; Ben > Skeggs; Dave Airlie > Subject: Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM