|
|
|
|
|
|
|
Re: Using Egit on svn repo [message #753343 is a reply to message #749880] |
Tue, 25 October 2011 20:40 |
Robin Rosenberg Messages: 332 Registered: July 2009 |
Senior Member |
|
|
R Shapiro skrev 2011-10-25 15.49:
> These are nothing very special, just simple external tool launchers that run command-line git. Here's a detailed example
>
> Main section:
>
> Location: ${git_exec}
> Working directory: ${git_work_tree}
> Arguments: svn fetch
>
> I have a whole set of these checked in as part of the repository (see the Shared File option in the Common section). Most are for git svn operations: 'svn fetch' , 'svn
> dcommit', 'svn rebase' etc. Others are for other operations not yet supported by egit, for example 'stash', or for operations that are more efficiently done with
> command-line Git, for example 'log --stat ${git_branch} ^trunk'
>
> The variables git_work_tree and git_branch are part of egit. On the other hand git_exec is my own String Substitution variable whose value is the location of the Git
> executable. I use a String Substitution variable rather than absolute path for the executable so that I can share these launchers with other team members who have Git
> installed in another location. For instance mine is defined as /usr/local/git/bin/git while other team members want C:\something\git
Glad you found them. I added these variables for exactly these kind of things,
although it turns out I use them mostly for accessing a converted objects from
a Clearcase view :(
The full set of variables are:
git_branch
git_dir
git_work_tree
git_repo_relative_path
The last one is the variable that allows me to map to other tools. By default they relate
to the currently selected resource. Optionally you can add an explicit resource name after the
colon: e.g. ${git_dir:MyProject}
Adding git_exec might be an idea, since EGit actually tries to figure out where there is a command
line version. EGit wants to know since there is a system-level gitconfig file, that contains
important settings, especially on Windows. git_prefix might be a more appropriate name, and you'd then
use ${git_prefix}/bin/git for the command line.
-- robin
|
|
|
|
Powered by
FUDForum. Page generated in 0.06973 seconds