EGit is terrible. I recommend SourceTree as a nice GUI for Git. It certainly makes it easier to do advanced things with resolving merge conflicts.
For what it's worth, the instructions here: http://wiki.apache.org/logging/UsingGitWithLogging with slight adaptions worked quite well. However, there are limitations with using this due to Subversion. For instance, you need to keep your repository history linear in order to properly commit back to svn. On 5 August 2014 10:43, Ralph Goers <ralph.go...@dslextreme.com> wrote: > I will vote +0. With Intellij one is just as seamless as the other and to > date I have found ways around needing branches. > > Ralph > > On Aug 5, 2014, at 8:22 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > > I am -0. SVN does not get in my way. Git is cool, OK, and like the > commit/push split, but I find the Eclipse SVN tooling a little easier to > deal with than EGit. For example, Subclipse provides an SVN Console but > EGit does not. > > Gary > > > On Tue, Aug 5, 2014 at 10:18 AM, Matt Sicker <boa...@gmail.com> wrote: > >> This topic was brought up elsewhere, so I'd like to propose a vote on >> switching to Git. >> >> +1 for me >> >> -- >> Matt Sicker <boa...@gmail.com> >> > > > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > Java Persistence with Hibernate, Second Edition > <http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory > > > -- Matt Sicker <boa...@gmail.com>
