From: Michelle S O. <ms...@ny...> - 2008-07-27 12:32:59
|
We've handled it on the build machine, but not for our local machines. The easiest thing I can think of to do for now is to add read permission to that directory so you could scp the jar. Would that help? ----- Original Message ----- From: Andrew Case <ac...@co...> Date: Sunday, July 27, 2008 1:26 am Subject: Re: [Gitclipse-devel] Can't get plugin to associate To: Han Chiu <dev...@gm...> Cc: gitclipse-devel <git...@li...> > Michelle/Patrick, > > Have we set up a way yet to automate grabbing the last successful > build of > javagit, building a jar, and slapping it into our javagit plugin? > Anything I can do to help set this up? This would be really useful > since > they're making daily fixes, it's really tedious to have to do it by hand. > > -- > Drew > > > On Sun, 27 Jul 2008, Han Chiu wrote: > > > The problem you guys are having with GitRm is a bug in the JavaGit API, > > GitRm is not extracting the relative path of the files you pass in, > instead > > it is doing a file.getAbsolutePath. So it was impossible to delete > a file > > at all. I've filed a bug report and James has checked in the fix > as of > > yesterday. See if your API is updated, if not, update it and you > should be > > able to invoke GitRm > > > > On Sun, Jul 27, 2008 at 12:47 AM, Patrick Winters > > <pat...@ny...>wrote: > > > >> Excuse me, accidentally hit ctrl-enter... > >> > >> The Eclipse platform handles everything until > >> GitTeamProviderType.metaFilesDetected(). > >> > >> This is because of the entry in plugin.xml > >> <extension > >> point="org.eclipse.team.core.repository"> > >> <repository > >> class="edu.nyu.cs.gitclipse.core.GitTeamProvider" > >> id="edu.nyu.cs.gitclipse.core.gitnature" > >> metaFilePaths=".git/config,.project" > >> typeClass="edu.nyu.cs.gitclipse.core.GitTeamProviderType"> > >> </repository> > >> </extension> > >> > >> GitAutoAssociateJob.associate() should get called within there somewhere > >> from its instance. This background job double checks the folder is > a git > >> project, and should call GitProviderPlugin.map(IProject). There's > a couple > >> things in here like GitProviderPlugin.isManagedByGit() (which should > >> determine if it's a valid GIT project) that could have bugs. > >> > >> > >>> -----Original Message----- > >>> From: Andrew Case [mailto:ac...@co...] > >>> Sent: Sunday, July 27, 2008 12:40 AM > >>> To: Patrick Winters > >>> Cc: 'Andrew Case'; 'gitclipse-devel' > >>> Subject: RE: [Gitclipse-devel] Can't get plugin to associate > >>> > >>> Where is the code that's called on a refresh to try to do the mapping? > >>> I > >>> want to put in some debug statements to see what seems to be amiss. > >>> > >>> Thanks, > >>> > >>> -- > >>> Drew > >>> > >>> > >>>> I can't say for sure. I haven't tested all the possibilities. > But if > >>> you > >>>> create a .git/config file in the project root, when the project is > >>> refreshed > >>>> the listener is fired... GitTeamProviderType.metaFilesDetected(). > >>> This is > >>>> because .git/config and .project are registered in the core > >>> plugin.xml file > >>>> as meta files for our team provider. If you find a situation where > >>> the > >>>> auto-associate is failing, add a regression test. Right now, if > a > >>> refresh > >>>> finds a .git/config file it should try and map the project to our > >>> team > >>>> provider. > >>>> > >>>>> -----Original Message----- > >>>>> From: Andrew Case [mailto:ac...@co...] > >>>>> Sent: Sunday, July 27, 2008 12:24 AM > >>>>> To: Michelle S Osborne > >>>>> Cc: Patrick Winters; 'gitclipse-devel' > >>>>> Subject: Re: [Gitclipse-devel] Can't get plugin to associate > >>>>> > >>>>> Michelle, > >>>>> > >>>>> My build was working fine under windows, but I was suspicious that > >>> git- > >>>>> rm > >>>>> wasn't working properly with cygwin/git, so I switched to linux > to > >>>>> check > >>>>> out it out and I am getting the same Null pointer exception when > I > >>> try > >>>>> the > >>>>> share project method. Did you figure out the cause? > >>>>> > >>>>> Patrick, > >>>>> > >>>>> Also, I haven't been able to get the automatic association thing > to > >>>>> work > >>>>> either. What is the order in which the directory/project/git-init > >>> need > >>>>> to > >>>>> be setup in order for it to associate? > >>>>> > >>>>> -- > >>>>> Drew > >>>>> > >>>>> > >>>>> On Sat, 26 Jul 2008, Michelle S Osborne wrote: > >>>>> > >>>>>> It is an older workspace. Selecting Share Project -> NYU Git Config > >>>>> gives me a NullPointerException (stacktrace included below): > >>>>>> > >>>>>> java.lang.NullPointerException > >>>>>> at > >>>>> > >>> edu.nyu.cs.gitclipse.ui.wizards.ConfigurationWizard.addPages(Configurat > >>>>> ionWizard.java:72) > >>>>>> at > >>>>> > >>> org.eclipse.team.internal.ui.wizards.ConfigureProjectWizardMainPage$1.s > >>>>> electionChanged(ConfigureProjectWizardMainPage.java:144) > >>>>>> at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:162) > >>>>>> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) > >>>>>> at org.eclipse.core.runtime.Platform.run(Platform.java:857) > >>>>>> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:46) > >>>>>> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:199) > >>>>>> at > >>>>> > >>> org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160) > >>>>>> at > >>>>> > >>> org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredVi > >>>>> ewer.java:2047) > >>>>>> at > >>>>> > >>> org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewe > >>>>> r.java:1138) > >>>>>> at > >>>>> > >>> org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredV > >>>>> iewer.java:1168) > >>>>>> at > >>>>> > >>> org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.jav > >>>>> a:227) > >>>>>> at > >>>>> org.eclipse.jface.util.OpenStrategy.access$3(OpenStrategy.java:221) > >>>>>> at > >>>>> > >>> org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:388 > >>>>> ) > >>>>>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) > >>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1495) > >>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1519) > >>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1504) > >>>>>> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1295) > >>>>>> at > >>>>> org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3350) > >>>>>> at > >>> org.eclipse.swt.widgets.Control.sendTrackEvents(Control.java:2758) > >>>>>> at > >>>>> > >>> org.eclipse.swt.widgets.Control.kEventControlTrack(Control.java:1961) > >>>>>> at org.eclipse.swt.widgets.Widget.controlProc(Widget.java:367) > >>>>>> at org.eclipse.swt.widgets.Display.controlProc(Display.java:827) > >>>>>> at org.eclipse.swt.internal.carbon.OS.CallNextEventHandler(Native > >>>>> Method) > >>>>>> at org.eclipse.swt.widgets.Table.kEventMouseDown(Table.java:2156) > >>>>>> at org.eclipse.swt.widgets.Widget.mouseProc(Widget.java:1262) > >>>>>> at org.eclipse.swt.widgets.Display.mouseProc(Display.java:2815) > >>>>>> at org.eclipse.swt.internal.carbon.OS.SendEventToEventTarget(Native > >>>>> Method) > >>>>>> at > >>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2934) > >>>>>> at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) > >>>>>> at org.eclipse.jface.window.Window.open(Window.java:796) > >>>>>> at > >>>>> > >>> org.eclipse.team.internal.ui.actions.ConfigureProjectAction$1.run(Confi > >>>>> gureProjectAction.java:53) > >>>>>> at > >>>>> > >>> org.eclipse.team.internal.ui.actions.TeamAction$2.run(TeamAction.java:2 > >>>>> 37) > >>>>>> at > >>>>> > >>> org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) > >>>>>> at > >>>>> > >>> org.eclipse.team.internal.ui.actions.TeamAction.run(TeamAction.java:234 > >>>>> ) > >>>>>> at > >>>>> > >>> org.eclipse.team.internal.ui.actions.ConfigureProjectAction.execute(Con > >>>>> figureProjectAction.java:45) > >>>>>> at > >>>>> > >>> org.eclipse.team.internal.ui.actions.TeamAction.run(TeamAction.java:481 > >>>>> ) > >>>>>> at > >>>>> > >>> org.eclipse.team.internal.ui.actions.TeamAction.runWithEvent(TeamAction > >>>>> .java:515) > >>>>>> at > >>>>> > >>> org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:246 > >>>>> ) > >>>>>> at > >>>>> > >>> org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(A > >>>>> ctionContributionItem.java:546) > >>>>>> at > >>>>> > >>> org.eclipse.jface.action.ActionContributionItem.access$2(ActionContribu > >>>>> tionItem.java:490) > >>>>>> at > >>>>> > >>> org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionCon > >>>>> tributionItem.java:402) > >>>>>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) > >>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1495) > >>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1519) > >>>>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1504) > >>>>>> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1295) > >>>>>> at > >>>>> org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3350) > >>>>>> at > >>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2950) > >>>>>> at > >>>>> org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) > >>>>>> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) > >>>>>> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) > >>>>>> at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) > >>>>>> at > >>>>> > >>> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java > >>>>> :289) > >>>>>> at > >>>>> > >>> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java: > >>>>> 461) > >>>>>> at > >>>>> org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > >>>>>> at > >>>>> > >>> org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplica > >>>>> tion.java:106) > >>>>>> at > >>>>> > >>> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle. > >>>>> java:169) > >>>>>> at > >>>>> > >>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplica > >>>>> tion(EclipseAppLauncher.java:106) > >>>>>> at > >>>>> > >>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Ecli > >>>>> pseAppLauncher.java:76) > >>>>>> at > >>>>> > >>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java > >>>>> :363) > >>>>>> at > >>>>> > >>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java > >>>>> :176) > >>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > >>>>>> at > >>>>> > >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja > >>>>> va:39) > >>>>>> at > >>>>> > >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso > >>>>> rImpl.java:25) > >>>>>> at java.lang.reflect.Method.invoke(Method.java:585) > >>>>>> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508) > >>>>>> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) > >>>>>> at org.eclipse.equinox.launcher.Main.run(Main.java:1173) > >>>>>> at org.eclipse.equinox.launcher.Main.main(Main.java:1148) > >>>>>> > >>>>>> > >>>>>> ----- Original Message ----- > >>>>>> From: Patrick Winters <pat...@ny...> > >>>>>> Date: Saturday, July 26, 2008 3:55 pm > >>>>>> Subject: RE: [Gitclipse-devel] Can't get plugin to associate > >>>>>> To: 'Michelle S Osborne' <ms...@ny...>, 'Andrew Case' > >>>>> <ac...@co...> > >>>>>> Cc: 'gitclipse-devel' <git...@li...> > >>>>>> > >>>>>>>> I'm not sure whether this is a related problem, but since > >>> updating > >>>>> this > >>>>>>>> morning I no longer have any gitclipse commands available in > the > >>>>> team > >>>>>>>> menu. There is a .git folder beneath the project root, so as > far > >>> as > >>>>>>> I > >>>>>>>> know the project should auto-associate. Is there something else > >>>>> that > >>>>>>>> has to be done for that to happen? > >>>>>>> > >>>>>>> Try a project refresh? Is this an older workspace that was > >>> created > >>>>> before > >>>>>>> the plugin changes? The metaFilesDetected() method might only > >>> fire > >>>>>>> when the > >>>>>>> meta file .git/config is new. But if a project and the meta info > >>>>> has > >>>>>>> existed and it's not new or changed, the listener might not get > >>>>> fired. > >>>>>>> Use > >>>>>>> the "share project" thing and map it to git manually. > >>>>>>> > >>>>>>>> Are we making the assumption that there is always a .git folder > >>>>> beneath > >>>>>>>> the project root? What should happen if there are multiple > >>> projects > >>>>>>> and > >>>>>>>> the .git folder is above the projects in the filesystem - does > >>> that > >>>>>>>> mean that the project is not associated with a git repository? > >>>>>>> > >>>>>>> That's a good question. The auto-associate is fired when a new > >>>>>>> project is > >>>>>>> created also, because it listens for .project as well. We could > >>>>>>> always run > >>>>>>> a git info to check on a new project to see if it's a git project. > >>>>> It > >>>>>>> also > >>>>>>> means that the isManagedByGit (GitProviderPlugin) method would > >>> need > >>>>> to > >>>>>>> be > >>>>>>> changed to test for this as well. > >>>>>>> > >>>>>>>> Currently commit expects the .git folder to be directly > >>> underneath > >>>>> the > >>>>>>>> project, and is limited to only working with resources from one > >>>>>>>> project. I can add support for multiple projects/repositories > in > >>>>> later. > >>>>>>> > >>>>>>> I think we should talk about this next week. How are we going > to > >>>>> deal > >>>>>>> with > >>>>>>> repositories that have multiple projects? In subversion you just > >>>>>>> check out > >>>>>>> from the path you want, but we can't do that can we? We could > >>> allow > >>>>>>> you to > >>>>>>> import a project from the filesystem, but not copy it. Your > >>> project > >>>>> points > >>>>>>> to the path in the git working copy you wish to use? > >>>>>>> > >>>>>>>> If commit gets wrapped up in a timely fashion, I'd be happy to > >>> work > >>>>>>> on > >>>>>>>> status next. After doing commit I have a pretty good idea of > how > >>> to > >>>>>>>> implement it. > >>>>>>>> > >>>>>>>> Michelle > >>>>>>>> > >>>>>>>> ----- Original Message ----- > >>>>>>>> From: Andrew Case <ac...@co...> > >>>>>>>> Date: Saturday, July 26, 2008 0:09 am > >>>>>>>> Subject: Re: [Gitclipse-devel] Can't get plugin to associate > >>>>>>>> To: Andrew Case <ac...@co...> > >>>>>>>> Cc: gitclipse-devel <git...@li...> > >>>>>>>> > >>>>>>>>> Oh, I got Han's fix which seemed to work. I had figured he'd > >>>>>>>> commited > >>>>>>>>> it > >>>>>>>>> to the repo. I went ahead and did that, so it's fixed in head. > >>>>>>>>> > >>>>>>>>> -- > >>>>>>>>> Drew > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> On Fri, 25 Jul 2008, Andrew Case wrote: > >>>>>>>>> > >>>>>>>>>> Patrick, > >>>>>>>>>> > >>>>>>>>>> Yeah, I've already done this (otherwise it wouldn't be able > to > >>>>>>>>> compile let > >>>>>>>>>> alone run). I'm still just supposed to run the 'ui' plugin > as > >>> an > >>>>>>>> 'eclipse > >>>>>>>>>> application' right? > >>>>>>>>>> > >>>>>>>>>> -- > >>>>>>>>>> Drew > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> On Fri, 25 Jul 2008, Andrew Case wrote: > >>>>>>>>>> > >>>>>>>>>>> Yes, we created a new project that wraps the javagit jar. > You > >>>>> need > >>>>>>>>> to check > >>>>>>>>>>> it out. Flip through the mailing list archives. You'll > need to > >>>>>>>> package > >>>>>>>>>>> javagit and copy the jar into our javagit project directory. > >>>>>>>>>>> > >>>>>>>>>>>> -----Original Message----- > >>>>>>>>>>>> From: gitclipse-devel-bounces@li... [mailto:gitclipse- > >>>>>>>>>>>> devel-bounces@li...] On Behalf Of Paul Munson Bethe > >>>>>>>>>>>> Sent: Wednesday, July 23, 2008 4:59 PM > >>>>>>>>>>>> To: Andrew Case > >>>>>>>>>>>> Cc: gitclipse-devel > >>>>>>>>>>>> Subject: Re: [Gitclipse-devel] Can't get plugin to associate > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> "out of memory" sounds like an infinite loop. > >>>>>>>>>>>> > >>>>>>>>>>>> btw - I get the error > >>>>>>>>>>>> > >>>>>>>>>>>> Bundle 'edu.nyu.cs.javagit' cannot be resolved > >>>>>>>>>>>> > >>>>>>>>>>>> in the core meta-inf file. > >>>>>>>>>>>> > >>>>>>>>>>>> Any thoughts? > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> ----- Original Message ----- > >>>>>>>>>>>> From: Andrew Case <acase@co...> > >>>>>>>>>>>> Date: Wednesday, July 23, 2008 9:42 am > >>>>>>>>>>>> Subject: Re: [Gitclipse-devel] Can't get plugin to associate > >>>>>>>>>>>> To: gitclipse-devel <gitclipse-devel@li...> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>>> The error I get when I do this is... > >>>>>>>>>>>>> > >>>>>>>>>>>>> I get a ConfigurationWizard.error > >>>>>>>>>>>>> Reason: > >>>>>>>>>>>>> Could not instantiate provider > >>>>>>>>>>>>> edu.nyu.cs.gitclipse.core.GitTeamProvider for > >>>>>>>>>>>>> project test. > >>>>>>>>>>>>> > >>>>>>>>>>>>> -- > >>>>>>>>>>>>> Drew > >>>>>>>>>>>>> > >>>>>>>>>>>>> On Tue, 22 Jul 2008, pmb309@ny... wrote: > >>>>>>>>>>>>> > >>>>>>>>>>>>>> Does 'Team -> Share -> NYU Git' not work? > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> ------Original Message------ > >>>>>>>>>>>>>> From: Andrew Case > >>>>>>>>>>>>>> Sender: gitclipse-devel-bounces@li... > >>>>>>>>>>>>>> To: gitclipse-devel > >>>>>>>>>>>>>> Sent: Jul 21, 2008 11:50 PM > >>>>>>>>>>>>>> Subject: [Gitclipse-devel] Can't get plugin to associate > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Has anyone else been having a problem getting the gitclipse > >>>>>>>> plugins > >>>>>>>>>>>>> to > >>>>>>>>>>>>>> associate themselves with projects? I don't seem to be > able > >>>>>>> to > >>>>>>>>>>>> associate > >>>>>>>>>>>>>> or create/import new projects during a runtime test. All > >>>>>>>> options > >>>>>>>>>>>>> seem to > >>>>>>>>>>>>>> error out with different error messages. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> If I go from the Menu->Git->Init or Clone I get: > >>>>>>>>>>>>>> "The chosen operation is not currently available" > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Import->Git->Clone > >>>>>>>>>>>>>> The selected wizard could not be started. > >>>>>>>>>>>>>> Plug-in edu.nyu.cs.gitclipse.ui was unable to load class > >>>>>>>>>>>>>> edu.nyu.cs.gitclipse.ui.wizards.GitCloneWizard > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Import->Git->Import > >>>>>>>>>>>>>> The selected wizard could not be started. > >>>>>>>>>>>>>> Plug-in edu.nyu.cs.gitclipse.ui was unable to load class > >>>>>>>>>>>>>> edu.nyu.cs.gitclipse.ui.wizards.GitImportWizard > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> New->Git->Init > >>>>>>>>>>>>>> The selected wizard could not be started. > >>>>>>>>>>>>>> Plug-in edu.nyu.cs.gitclipse.ui was unable to load class > >>>>>>>>>>>>>> edu.nyu.cs.gitclipse.ui.wizards.GitInitWizard > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Also, when running the plugin I get "out of memory" errors > >>> a > >>>>>>>> lot. > >>>>>>>>>>>> I > >>>>>>>>>>>>>> don't get this when just running my standard eclipse, > so it > >>>>>>> has > >>>>>>>>> to > >>>>>>>>>>>> be > >>>>>>>>>>>>>> related to the plugin. Does anyone else have this problem? > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> -- > >>>>>>>>>>>>>> Drew > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> ----------------------------------------------------------- > >>> -- > >>>>> -- > >>>>>>>> ---- > >>>>>>>>>>>> ------ > >>>>>>>>>>>>>> This SF.Net email is sponsored by the Moblin Your Move > >>>>>>>> Developer's > >>>>>>>>>>>> challenge > >>>>>>>>>>>>>> Build the coolest Linux based applications with Moblin > SDK > >>> & > >>>>>>>> win > >>>>>>>>>>>>> great prizes > >>>>>>>>>>>>>> Grand prize is a trip for two to an Open Source event > >>>>> anywhere > >>>>>>>> in > >>>>>>>>>>>>> the world > >>>>>>>>>>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >>>>>>>>>>>>>> _______________________________________________ > >>>>>>>>>>>>>> Gitclipse-devel mailing list > >>>>>>>>>>>>>> Gitclipse-devel@li... > >>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/gitclipse- > >>> devel > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Sent via BlackBerry > >>>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> ------------------------------------------------------------ > >>> -- > >>>>> -- > >>>>>>>> ----- > >>>>>>>>>>>> ---- > >>>>>>>>>>>>> This SF.Net email is sponsored by the Moblin Your Move > >>>>>>>> Developer's > >>>>>>>>>>>> challenge > >>>>>>>>>>>>> Build the coolest Linux based applications with Moblin > SDK & > >>>>>>> win > >>>>>>>>>>>> great > >>>>>>>>>>>>> prizes > >>>>>>>>>>>>> Grand prize is a trip for two to an Open Source event > >>> anywhere > >>>>>>>> in > >>>>>>>>> the > >>>>>>>>>>>>> world > >>>>>>>>>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >>>>>>>>>>>>> _______________________________________________ > >>>>>>>>>>>>> Gitclipse-devel mailing list > >>>>>>>>>>>>> Gitclipse-devel@li... > >>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/gitclipse-devel > >>>>>>>>>>>> > >>>>>>>>>>>> ------------------------------------------------------------- > >>> -- > >>>>> -- > >>>>>>>> ------ > >>>>>>>>>>>> -- > >>>>>>>>>>>> This SF.Net email is sponsored by the Moblin Your Move > >>>>>>>> Developer's > >>>>>>>>>>>> challenge > >>>>>>>>>>>> Build the coolest Linux based applications with Moblin > SDK & > >>>>> win > >>>>>>>> great > >>>>>>>>>>>> prizes > >>>>>>>>>>>> Grand prize is a trip for two to an Open Source event > >>> anywhere > >>>>>>> in > >>>>>>>>> the > >>>>>>>>>>>> world > >>>>>>>>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >>>>>>>>>>>> _______________________________________________ > >>>>>>>>>>>> Gitclipse-devel mailing list > >>>>>>>>>>>> Gitclipse-devel@li... > >>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/gitclipse-devel > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> --------------------------------------------------------------- > >>> -- > >>>>> -- > >>>>>>>> ------ > >>>>>>>>>> This SF.Net email is sponsored by the Moblin Your Move > >>>>> Developer's > >>>>>>>> challenge > >>>>>>>>>> Build the coolest Linux based applications with Moblin SDK > & > >>> win > >>>>>>>>> great prizes > >>>>>>>>>> Grand prize is a trip for two to an Open Source event anywhere > >>> in > >>>>>>>>> the world > >>>>>>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >>>>>>>>>> _______________________________________________ > >>>>>>>>>> Gitclipse-devel mailing list > >>>>>>>>>> Git...@li... > >>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/gitclipse-devel > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> ---------------------------------------------------------------- > >>> -- > >>>>> --- > >>>>>>>> ---- > >>>>>>>>> This SF.Net email is sponsored by the Moblin Your Move > >>> Developer's > >>>>>>>> challenge > >>>>>>>>> Build the coolest Linux based applications with Moblin SDK & > win > >>>>>>>> great > >>>>>>>>> prizes > >>>>>>>>> Grand prize is a trip for two to an Open Source event anywhere > >>> in > >>>>>>> the > >>>>>>>>> world > >>>>>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >>>>>>>>> _______________________________________________ > >>>>>>>>> Gitclipse-devel mailing list > >>>>>>>>> Git...@li... > >>>>>>>>> https://lists.sourceforge.net/lists/listinfo/gitclipse-devel > >>>>>>>> > >>>>>>>> ----------------------------------------------------------------- > >>> -- > >>>>> ---- > >>>>>>>> -- > >>>>>>>> This SF.Net email is sponsored by the Moblin Your Move > >>> Developer's > >>>>>>>> challenge > >>>>>>>> Build the coolest Linux based applications with Moblin SDK & > win > >>>>> great > >>>>>>>> prizes > >>>>>>>> Grand prize is a trip for two to an Open Source event > anywhere in > >>>>> the > >>>>>>>> world > >>>>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >>>>>>>> _______________________________________________ > >>>>>>>> Gitclipse-devel mailing list > >>>>>>>> Git...@li... > >>>>>>>> https://lists.sourceforge.net/lists/listinfo/gitclipse-devel > >>>>>>> > >>>>>> > >>>>>> ------------------------------------------------------------------- > >>> -- > >>>>> ---- > >>>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's > >>>>> challenge > >>>>>> Build the coolest Linux based applications with Moblin SDK & win > >>>>> great prizes > >>>>>> Grand prize is a trip for two to an Open Source event anywhere > in > >>> the > >>>>> world > >>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >>>>>> _______________________________________________ > >>>>>> Gitclipse-devel mailing list > >>>>>> Git...@li... > >>>>>> https://lists.sourceforge.net/lists/listinfo/gitclipse-devel > >>>>>> > >>>> > >> > >> > >> ------------------------------------------------------------------------- > >> This SF.Net email is sponsored by the Moblin Your Move Developer's > >> challenge > >> Build the coolest Linux based applications with Moblin SDK & win great > >> prizes > >> Grand prize is a trip for two to an Open Source event anywhere in > the world > >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >> _______________________________________________ > >> Gitclipse-devel mailing list > >> Git...@li... > >> https://lists.sourceforge.net/lists/listinfo/gitclipse-devel > >> > > > > > > > > -- > > Han Chiu > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Gitclipse-devel mailing list > Git...@li... > https://lists.sourceforge.net/lists/listinfo/gitclipse-devel |