$ git clone git://dev.eclipse.org/org.eclipse.jface/org.eclipse.jface.text.git [.. snip ..] $ cd org.eclipse.jface.text $ git log --grep='275686' commit a7d0c902cae6382be0b0812a773f651f75a801d8 Author: mkellerThen I opened my 3.5.2RC3 carbon build of eclipse, imported the org.eclipse.jface.text project, and File->Export->Deployable plug-ins and fragments. Choose Install into host, and restart the workbench. Voila, Silenio was correct and that commit solved the issue. All told, the above took about 10 minutes, and left enough time for me to sing the praises of git usage at Eclipse in this blog post before I had to be out the door.Date: Thu Oct 8 19:22:34 2009 +0000 Bug 275686: [painting] Rulers should not draw outside of SWT.Paint $ git checkout -b b294929 origin/R3_5_maintenance $ git cherry-pick a7d0c902c Finished one cherry-pick. # On branch b294929 # Your branch is ahead of 'origin/R3_5_maintenance' by 1 commit.
Friday, February 12, 2010
More praise for git at Eclipse
Yesterday, @iamkevb tweeted: #SWT needs help with a carbon bug on 10.6. If you have time and hardware, attach patches to http://bugs.eclipse.org/294929. I happened to have the hardware to test it, so I downloaded a few carbon builds, and succeeded in reproducing the error using the steps posted to bugzilla. Luckily, I found that the latest 3.6 integration build didn't exhibit the same error. Now, I'm no carbon programmer, so I just posted my results as a comment, hoping that someone who knew more about SWT would be able to deduce what changed between 3.5.2RC3 and the latest in the 3.6 integration build. Today, Silenio Quarti posted that he believed the error was fixed as a result of bug #275686. Now, this is where it git comes in.
I only had about 30 minutes before I had to be out the door, but I figured that would be plenty of time to whether Silenio was correct. I headed over to http://dev.eclipse.org/git/ to find out the URL for the jface.text project (turned out bug 275686 was a jface change, and didn't even touch the Carbon bindings specifically).
Subscribe to:
Post Comments (Atom)
2 comments:
Cool stuff but I think who you're praising is wrong. Git deserves no special praise in this scenario as any modern version control system could had played the same role with the same results. Eclipse's use of social media like Twitter to communicate with their community and open source in general are where the real praise should go. Eclipse++
I definitely agree that the Eclipse folks did a lot to make the above scenario possible. Extensive use of bugzilla, with commit messages properly tagged with the relevant bug id was also vital.
Really, the part about git that made the above scenario so enjoyable was the speed of it all. Obviously, I could have done all the above even with just CVS (which is what most [all?] Eclipse projects still use as their canonical source repository), but I doubt I could have done it in 15 minutes.
Post a Comment