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 native git; > of course there's no need to consider proxy settings at all. It > will use http proxy set by eclipse itself. Lianhao said it's > difficult for him to set proxy and call it through shell. So, use > egit clone is his requirement. > > So, if we want to use it for clone project. > 1. One way: User must install egit, then we try to hack the code, > directly call the egit related UI Wizard during > poky-meta-project creation phase.. Risk is: Egit is in > incubation. I did meet some errors when checkout, > (NULLPointer...). If user does not install it, create project will > fail. > 2. Another way: We study the code, get rid of useless code, only > extract clone related code. > Risk is: git repository is implemented as a whole, UI are > complex too. The code amount is huge. > > So my question is: Since poky.git is the only destination, we need > not consider support all sorts of repositories at all. Also, if > user want to bitbake, he must configure his git well (such as > proxy problem). I am not sure how shell git works now and is it > totally intolerable? We need egit's implementation instead of current > shell script implementation. I'm not sure I quite understand this requirement. My expectation is user will have one local git clone per project which they can use either from the command line or Eclipse IDE. I'm worried about your statement of EGIT implemented its own git, does this mean if our project cloned through egit, user can't access it from the command line?
Also, I'm not quite sure about Lianhao's issue, currently the git clone is the same command as you'll clone a poky repo from command line, why it's an issue? There's no specific thing, i.e. proxy setting you need to do as far as you can do git clone from command line... > > 2) You want to support commit, diff, patch, cherry pick, etc. > It's no problem. Actually it's what egit is supposed to do. > > After user create poky-meta-project successfully, he will click > the project, then Select->Team->Share->git, a local repository is > set up. commit, diff, branch, anything is not a problem. Poky does > not allow submit changes to remote repository, so user can only > have local repository to track their changes. I need some clarification on this, so this will also require user install EGIT I guess, right? By saying "click the project, then Select->Team->Share->git, a local repository is set up." Isn't the local repository already setup during during the project creation through git clone? Can EGIT just point to that repo and do the git functions? As to only do interaction with local repo, I think that's fine as the first step... > > > So I guess the only problem left here is that whether we should try > extract egit internal clone Functionality. If yes, which way 1) > install egit and hack the UI code 2) study the code, extract > needed code. Both risks have been listed above. > > Thanks & Regards, > criping > > >> -----Original Message----- >> From: Zhang, Jessica >> Sent: Thursday, January 06, 2011 12:57 PM >> To: Ke, Liping; Lu, Lianhao; Tian, Kevin >> Cc: yocto@yoctoproject.org >> Subject: RE: Eclipse Plugin EGit investigation result >> >> 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
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
