[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] git (was:The Great Managed Build API Tooling Fiasco of 2009)
|
BTW, I'm closely tracking the git situation. It is my sense that git
will help us immensely, even dealing with API changes after the release
as Elena mentions (i.e., do it in your git repo and contribute it to the
master later).
So, Chris, I will get you started ;). I'd like to know the CDT
community's opinion on this. One thing that Mike challenged us at the
council meetings at EclipseCon was for a high profile project to step up
and say they would like to move to git before the Foundation would
seriously invest in it. Personally, I'd like the CDT to be one of the
first. What do you think?
Doug.
________________________________
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Chris Recoskie
Sent: Wednesday, April 22, 2009 7:57 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] The Great Managed Build API Tooling Fiasco of
2009
I agree, but don't get me started :-P
===========================
Chris Recoskie
Team Lead, IBM CDT and RDT
IBM Toronto
Jesper Eskilson <jesper.eskilson@xxxxxx>
Jesper Eskilson <jesper.eskilson@xxxxxx>
Sent by: cdt-dev-bounces@xxxxxxxxxxx
04/22/2009 03:40 AM
Please respond to
"CDT General developers list." <cdt-dev@xxxxxxxxxxx>
To
"CDT General developers list." <cdt-dev@xxxxxxxxxxx>
cc
Subject
Re: [cdt-dev] The Great Managed Build API Tooling Fiasco of 2009
Chris Recoskie wrote:
> My first instinct was to perhaps refactor these packages to use the
right
> naming convention, but then we lose the CVS history on them all, and
this
> affects a lot of classes :-(
You are using an antiquated version-control tool, you know that, right?
The rest of the (open source) world abandoned CVS a long time ago.
--
/Jesper
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
