Ke, Liping wrote:
> Hi, Jessica
>
> I verified that if we use git from shell to clone a tree first,
> create the new project, and then use egit to manage the project,
> everything is fine.
> It will detect that .git repository is there and will not repeatedly
> create one.
> So egit will not con
Hi, Jessica
I verified that if we use git from shell to clone a tree first, create the new
project, and then use egit to manage the project,
everything is fine.
It will detect that .git repository is there and will not repeatedly create
one.
So egit will not conflict with native command line gi
Ke, Liping wrote:
> Hi, Jessica
>
> After discussed with Lianhao, seems there're two requirements
>
> 1) Lianhao expect that we can use the capability of git clone
>functionality provided by egit. Egit is strong and implemented its
>own git, support all sorts of ops, so we need not use n
Hi, Jessica
After discussed with Lianhao, seems there're two requirements
1) Lianhao expect that we can use the capability of git clone functionality
provided by egit. Egit is strong and implemented its own git, support all
sorts of ops,
so we need not use native git; of course there's no
Liping,
Thanks for the thorough analysis of EGIT, as you pointed it mainly for team
setup which is not what we want. Can you download the source and see how it
interact with git and probably we can borrow some ideas to achieve some
simple git tasks, e.g. commit changes etc.
Thanks,
Jessica
Ke,
Hi, Jessica
I have tried the existing egit plugin. It is a true powerful plugin, but I am
afraid it can't be communicating well with poky-meta-project plugin.
Below is some details
advantages:
1. EGIT support all sorts of protocols, including ftp, ssh, git, http, so we
can easily pull/push the
