You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

TODO 2.0KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849
  1. = JGit Wishlist =
  2. Below are some of the areas that needs work. Also take a look at JGit
  3. related issues in the EGit project:
  4. - http://code.google.com/p/egit/issues/list?q=label:Component-JGit
  5. == Switch Branch ==
  6. Switch to an existing branch, updating the working directory to match.
  7. Note that updating the working directory may require a 3 way merge
  8. if the working directory is dirty (git checkout -m).
  9. My usual git working style is to not switch branches with a dirty
  10. working directory; I always commit to the current branch before
  11. switching to a new one. I mention that because I assume it'll be
  12. easier to implement that workflow first; once you have commit
  13. capability, you can do that style of branch switching (either
  14. preventing the switch or doing an implicit commit when the working
  15. directory is dirty) without having to worry about merging. ''--
  16. Steven Grimm''
  17. == Merge ==
  18. Merging changes from one local branch to another.
  19. Again, like fetch I'd like to keep egit/jgit 100% pure Java and
  20. implement merge-recursive in Java. We may need to invoke RCS
  21. merge if Eclipse doesn't have its own 3 way file merge algorithm
  22. available, or do what core Git just did and implement a 3 way in
  23. memory merge algorithm. git-merge-recursive is only 1336 lines of C
  24. so it should not be too difficult to port the algorithm to pure Java.
  25. == SVN Integration ==
  26. It would be swell -- but put it at the bottom of your priority list
  27. -- to have git-svn interoperability; sadly most of my git usage at
  28. the moment is in cloned svn repositories and it would be great if
  29. egit could do the right thing when the current git repo is cloned
  30. from svn. What "the right thing" is, exactly, is debatable, but I
  31. suppose some kind of integration with the Subclipse plugin is one
  32. possibility (and if nothing else, that plugin probably has code
  33. that can be reused.) I'd like to be able to update from and commit
  34. to the parent svn repository. ''-- Steven Grimm''
  35. I'm considering this to be out of scope for the time being, but if
  36. someone takes it on and submits reasonable patches we'll include
  37. them. ''-- Shawn Pearce''