From: Shawn Pearce <spearce@spearce.org>
Date: Mon, 04 Dec 2006 18:05:53 GMT
Subject: Re: egit/jgit wishlist
Message-ID: <20061204180553.GF6011@spearce.org>
In-Reply-To: <457461BF.6080706@midwinter.com>

Steven Grimm <koreth@midwinter.com> wrote:
> My usual git working style is to not switch branches with a dirty 
> working directory; I always commit to the current branch before 
> switching to a new one. I mention that because I assume it'll be easier 
> to implement that workflow first; once you have commit capability, you 
> can do that style of branch switching (either preventing the switch or 
> doing an implicit commit when the working directory is dirty) without 
> having to worry about merging.

It is easier to code.  :-)

But users have come to expect the three-way merge during branch
switches.  I actually get ticked when it fails, because that is
usually when I need it most.  Anyway, I also know a number of
Eclipse users who also use Git that would prefer it if the switch
fails on a dirty working tree, as that usually just means they
forgot to commit their changes first.
 
> And finally, it would be swell -- but put it at the bottom of your 
> priority list -- to have git-svn interoperability; sadly most of my git 
> usage at the moment is in cloned svn repositories and it would be great 
> if egit could do the right thing when the current git repo is cloned 
> from svn. What "the right thing" is, exactly, is debatable, but I 
> suppose some kind of integration with the Subclipse plugin is one 
> possibility (and if nothing else, that plugin probably has code that can 
> be reused.) I'd like to be able to update from and commit to the parent 
> svn repository.

SVN integration is probably out of scope for the plugin (at least
right now) but I won't reject any reasonable patches!  (hint hint)
:-)

--