[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] CDT compile errors after update from CVC
|
On Tue, Mar 2, 2010 at 4:13 PM, Andrew Gvozdev
<angvoz.dev@xxxxxxxxx> wrote:
On Tue, Mar 2, 2010 at 3:02 PM, Alex Blewitt
<alex.blewitt@xxxxxxxxx> wrote:
On 2 Mar 2010, at 18:42, Doug Schaefer wrote:
> Could it be possible that a snapshot was taken half way through someone's commit? ugh. Another good reason to move to git. Snapshots would be a lot easier to keep in sync.
Yes, it would be implicit in the way Git works ;-)
Denis was looking for volunteers for having a (read-only) Git repo modelled after their CVS repo:
http://aniszczyk.org/2010/01/29/calling-eclipse-org-projects-interested-in-git/
https://bugs.eclipse.org/bugs/show_bug.cgi?id=257706#c173
I don't know if CDT is 'too big' at the moment to host its repository(ies) and whether Denis already has enough, but has someone asked the question already?
Another thought is what the plan would be to break down the CDT projects into separate Git modules - one per project, or would some projects be co-mingled in Git repositories? Might as well plan for the eventualities :-)
The granularity seems to be exactly what I would start with.
Andrew
One point re: what would live where; you cannot do a 'partial' checkout of a Git repository; it's an all-or-nothing thing. So a project, along with a test fragment, might live in one repo and then a separate repo for a different project/etst fragment; or you might bundle all the DSF-GDB projects together (that's been a point of discussion recently :-)
Alex_______________________________________________
We definitely have to take a look at the structure before deciding the right approach. I'm not sure how they've set these repos up since there are symbolic links between them, especially from the cdt repo to the cdt-* ones. And this structure is very historical. It was how we set up the groups originally for controlling committer access. Now that we're one group, we've been putting everything new in the org.eclipse.cdt folder. I would like to see the structure more closely match the real plug-in dependency architecture. Maybe by feature?
But I really have bigger plans. I'd like us to use git for read/write, not just read. Once all the Eclipse process issues are worked out, I'd like to recommend us move. I know Eclipse Team integration support is an issue and the egit team is making great progress. Failing that, I've had great experiences with git-gui with my Android play-time projects, launching it as an External Tool. But we would need consensus from the committers to make the move. So think about it. Maybe dig into git a bit. And once Helios is out the door, we can take a good look at it.
