<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=91966#c91">Comment # 91</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=91966">bug 91966</a> from <a class="email" href="mailto:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>"> Kevin Brace</a> <pre>(In reply to Benno Schulenberg from <a href="show_bug.cgi?id=91966#c90">comment #90</a>) Hi Benno, > > First make sure all your changes are in patch files and safely outside of > your openchrome git repo. Then do 'git reset --hard HEAD'. > > Then do 'git checkout -b workingonvx855', which makes a branch. Then make > the changes (or apply the patch you already have) and commit it with 'git > commit -as', write a message describing the change, and save. You will have > made your first local commit. Then make more changes, then commit those. > And so on. > > When you're done, do 'git format-patch origin', and git will make several > patches for you that apply one after the other. You could also just look at > 'git log' or 'git log -p' when you're still busy. I did the patch generation a little differently, but after spending several hours, I figured out how to do it the way I wanted it done. That being said, your instructions were helpful, so thank you very much for helping me out. Regards, Kevin Brace</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>