git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Grimm <koreth@midwinter.com>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: egit/jgit wishlist
Date: Mon, 04 Dec 2006 09:58:23 -0800	[thread overview]
Message-ID: <457461BF.6080706@midwinter.com> (raw)
In-Reply-To: <20061204172836.GB6011@spearce.org>

I am definitely looking forward to a usable Eclipse plugin! A few comments:

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.

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.

-Steve

  reply	other threads:[~2006-12-04 17:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-04 17:28 egit/jgit wishlist Shawn Pearce
2006-12-04 17:58 ` Steven Grimm [this message]
2006-12-04 18:05   ` Shawn Pearce
2006-12-04 18:16 ` Grzegorz Kulewski
2006-12-04 18:29   ` Shawn Pearce
2006-12-04 21:19     ` Steven Grimm
2006-12-04 21:47       ` Grzegorz Kulewski
2006-12-04 22:06         ` Steven Grimm
2006-12-05  8:37         ` Johannes Schindelin
2006-12-04 21:54   ` Robin Rosenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=457461BF.6080706@midwinter.com \
    --to=koreth@midwinter.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).