Fine for me, if Mickael is ok with this approach. I just wanted to point out that this repo might (I have not checked recently) contain outdated projects.
Best regards, Lars 2015-01-09 14:18 GMT+01:00 Daniel Megert <[email protected]>: > The reason that repo wasn't used anymore, is because e4 stuff is now > usually directly done in the main platform.ui repo. For this experiment it > is the right choice. I wouldn't start a new repo just for that, and "tools" > repo is not the right place. > > Dani > > > > From: Lars Vogel <[email protected]> > To: E4 Project developer mailing list <[email protected]> > Date: 09.01.2015 13:44 > Subject: Re: [e4-dev] Wish to contribute smarter import mechanism > to e4 incubator. > Sent by: [email protected] > ------------------------------ > > > > > the benefit of yet-another-repo over contributing to the regular e4 repo? > > I would not call *http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/* > <http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/> our "regular" repo. > See *http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/log/* > <http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/log/> it is rarely > used these days. > > AFAIK the most activate repo is the e4 tools one, > *http://git.eclipse.org/c/e4/org.eclipse.e4.tools.git/* > <http://git.eclipse.org/c/e4/org.eclipse.e4.tools.git/> and most > sub-projects go their own Git repo in the past, see > *http://git.eclipse.org/c/?q=e4* <http://git.eclipse.org/c/?q=e4> > > The disadvantage of using > *http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/* > <http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/> might be that it > contains a lot of outdated stuff. I personally do not even clone that repo > anymore. > > Best regards, Lars > > 2015-01-09 9:53 GMT+01:00 Mickael Istria <*[email protected]* > <[email protected]>>: > On 01/09/2015 06:12 AM, Lars Vogel wrote: > I think that would be the correct way in case you plan to contribute more > of the tools you are working on to the e4 project. > Actually, I'm trying to contribute them directly to Platform first (cf > *https://bugs.eclipse.org/bugs/show_bug.cgi?id=427768* > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=427768> ). Only when > they're not considered as mature enough, the strategy is to put them in e4 > incubator. > What would be the benefit of yet-another-repo over contributing to the > regular e4 repo? > > Cheers, > -- > Mickael Istria > Eclipse developer at *JBoss, by Red Hat* <http://www.jboss.org/tools> > *My blog* <http://mickaelistria.wordpress.com/> - *My Tweets* > <http://twitter.com/mickaelistria> > > _______________________________________________ > e4-dev mailing list > *[email protected]* <[email protected]> > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > *https://dev.eclipse.org/mailman/listinfo/e4-dev* > <https://dev.eclipse.org/mailman/listinfo/e4-dev> > _______________________________________________ > e4-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/e4-dev > > _______________________________________________ > e4-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/e4-dev >
_______________________________________________ e4-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/e4-dev
