|
|
|
Re: View like Git GUI [message #692421 is a reply to message #692416] |
Mon, 04 July 2011 12:15 |
|
You can use also synchronize view (team -> synchronize workspace) to inspect local changes. If you would like to split changes into staged and un-staged you can use 'Git Change Set' model.
|
|
|
|
|
|
Re: View like Git GUI [message #693536 is a reply to message #692443] |
Wed, 06 July 2011 17:17 |
|
Jacek Kolodziejczyk wrote on Mon, 04 July 2011 08:53Good. Still the missing features in the synchronize perspective for me are:
- cannot set 'Git Change Set' as the default model
Yes you can, just go Preferences -> Tam -> Git and select "Automatically enable change set grouping in Git synchronize"
Jacek Kolodziejczyk wrote on Mon, 04 July 2011 08:53- flat presentation in preferences does not work for this model
This is already on my TODO list, same as compressed folder presentation
Jacek Kolodziejczyk wrote on Mon, 04 July 2011 08:53- missing patch format comparison, if the change is at then end then I have to scroll the whole file instead of seeing it instantly,
- I use black background for my code editors and the black file comparison guides are not visible for me
This seams like a general error in compare editor. I've see same problem in CVS integration.
Jacek Kolodziejczyk wrote on Mon, 04 July 2011 08:53
- should come with Git staging view or commit view open by default, I know I can add it once and then it will be reopened by the perspective next time, but still
I doubt that this would be useful, not every one like to have lots of views opened.
|
|
|
Re: View like Git GUI [message #702601 is a reply to message #693536] |
Tue, 26 July 2011 15:04 |
R Shapiro Messages: 386 Registered: June 2011 |
Senior Member |
|
|
If you want to use Git Gui itself, it's quite easy, since egit defines some handy variables. Just create an external launcher to run the executable 'git' with arguments 'gui', and the working directory set to ${git_work_tree}. When you run the launcher you'll get a Git Gui window for the repository of the currently selected file or directory.
Probably you would want to configure the launcher to refresh the workspace when it's done so that egit can update the modification decorations.
For a little more generality, in case you decide to share the launcher, define your own variable, for instance 'git_exec', and use that as that, instead of 'git', as the executable, Each developer can then define this variable to point at their local installation, wherever it happens to be.
Of course all this assumes you have an ordinary Git installed and you're not relying entirely on jgit.
|
|
|
Powered by
FUDForum. Page generated in 0.03308 seconds