Re: [cdt-dev] urge to use git rising...

["Schaefer, Doug" <Doug.Schaefer@xxxxxxxxxxxxx>]

I do believe it’s git cvsimport. And, yeah, I’d say it’s a fail.

 

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Terry Parker
Sent: Wednesday, December 08, 2010 2:43 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] urge to use git rising...

 

Are the webmasters using cvs2git rather than git-cvsimport to pull from CVS?  From what I can tell git-cvsimport is a complete FAIL.  I just lost 2+ days because the R3_6_maintenance branch of the JDT UI plugin was bleeding things from head into the maintenance branch.

 

--Terry

On Wed, Dec 8, 2010 at 11:23 AM, Andrew Gvozdev <angvoz.dev@xxxxxxxxx> wrote:

You could clone http://dev.eclipse.org/git/ on github and share it that way. One problem is that they pull from CVS once a day. I've been using such clone for scanner discovery and happy about it.

Andrew

 

On Wed, Dec 8, 2010 at 2:18 PM, Schaefer, Doug <Doug.Schaefer@xxxxxxxxxxxxx> wrote:

Hey gang,

I just thought I'd share this with you. I'm starting to work on Build
Config visualization feature for the Project Explorer and had a sudden
urge and subsequent disappointment over git for CDT. If we had git, I
could check my work into a quickly created branch. Everyone could try it
out and give feed back. We can keep working on it bit by bit, everyone
can contribute to it, and when finished I could merge it into master and
then delete the branch.

I'm not sure what shape the merge support is with egit, but we are using
it for internal plug-in development and it's OK so far. I can't wait
until we can revisit this for the CDT, hopefully in the summer.

Thanks for listening :)
Doug.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

 

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev