RE: [cdt-patch] cvs access

["Schaefer, Doug" <dschaefer@xxxxxxxxxxxx>]

I agree with Sebastien.  I can envision many scenarios where changes in the
core will require changes in the ui.

I then have a couple of questions, not yet being an expert in CVS:
1) Do modules have anything to do with committer status.
2) Is there a public way to get the list of committers for a given thing
(that being a module if the answer to 1 is true).

Thanks,
Doug

-----Original Message-----
From: Sebastien Marineau [mailto:sebastien@xxxxxxx] 
Sent: Tuesday, September 17, 2002 2:29 PM
To: 'cdt-patch@xxxxxxxxxxx'
Subject: RE: [cdt-patch] cvs access

Hi Don,

the modules list is kept by the webmaster at eclipse, so
I'll forward the change once we all agree. I'll list here 
the list of modules that you had (for everyone to comment on):

____________________________________________________

cdt -a cdt-core cdt-debug cdt-features cdt-ui 
  
cdt-core -a org.eclipse.cdt org.eclipse.cdt.core org.eclipse.cdt.core.linux
org.eclipse.cdt.core.qnx org.eclipse.cdt.core.solaris
org.eclipse.cdt.core.win32
 
cdt-debug -a org.eclipse.cdt.debug.core org.eclipse.cdt.debug.mi.core
org.eclipse.cdt.debug.mi.ui org.eclipse.cdt.debug.ui
org.eclipse.cdt.debug.ui.tests

cdt-features -a org.eclipse.cdt-features

cdt-launch -a org.eclipse.cdt.launch

cdt-ui -a org.eclipse.cdt.ui org.eclipse.cdt.ui.tests
___________________________________________________

I think the separation between cdt-cre and cdt-ui is a little artificial, so
how
about this instead:

cdt -a cdt-core cdt-debug cdt-features cdt-tests

cdt-core -a org.eclipse.cdt org.eclipse.cdt.core org.eclipse.cdt.core.linux
org.eclipse.cdt.core.qnx org.eclipse.cdt.core.solaris
org.eclipse.cdt.core.win32 org.eclipse.cdt.ui

cdt-debug -a org.eclipse.cdt.debug.core org.eclipse.cdt.debug.mi.core
org.eclipse.cdt.debug.mi.ui org.eclipse.cdt.debug.ui org.eclipse.cdt.launch

cdt-features -a org.eclipse.cdt org.eclipse.cdt-features

cdt-tests -a org.eclipse.cdt.debug.ui.tests org.eclipse.cdt.ui.tests

Basically, include launch with the debugger, and separate the tests as a
separate CVS module.
Would that still work for you? If so, I'll forward the change to Eclipse's
webmaster.


Sebastien




> -----Original Message-----
> From: Don Howard [mailto:dhoward@xxxxxxxxxx]
> Sent: Monday, September 16, 2002 7:55 PM
> To: cdt-patch@xxxxxxxxxxx
> Subject: [cdt-patch] cvs access
> 
> 
> 
> [I attempted to post this last week, but my post was rejected, 
> please pardon me if you see a duplicate message]
> 
> 
> 
> I noticed that the cvs modules for /home/tools don't seem to 
> match what's 
> in the repository.  This has been stopping me from being able 
> to check out 
> the CDT via command-line cvs.
> 
> I've attached a patch that attempts to correct this.  If the cvs owner
> chooses to apply this, please examine it closely before hand 
> -- I don't
> claim much in the way of cvs skills.
> 
> -- 
> dhoward@xxxxxxxxxx
> gdb engineering
> 
> 
> 
> 
> 
> 
_______________________________________________
cdt-patch mailing list
cdt-patch@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-patch