Hey, Marc, while I have you here, I imagine Theia will also need a gdb debug adapter. There was certainly a lot of buzz on Theia at EclipseCon and it should be on our list of supported IDEs as well. I actually think it does certain things
better than VS Code and am giving it a serious look. Hopefully we can work together on it.
From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx>
On Behalf Of Marc Dumais
Sent: Monday, October 29, 2018 2:31 PM
To: Nathan Ridge <zeratul976@xxxxxxxxxxx>; CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] CDT on Github
" I find them awkward having to work in a fork that needs to be magically kept up to date and stuff"
That's only true for non-committers, AFAIK. Committers should have required permissions to create branches on the main repo, so pull requests can originate from there,
rather than a fork, if preferred.
Good question. For the new repos, it would be Github Issues and Pull Requests. I actually find their Issues better than bugzilla. But I've never been a fan of Pull Requests, mainly because
For org.eclipse.cdt, I don't suggest any changes. Basically all we'd be doing is moving the existing repo,
https://github.com/eclipse/cdt, to our new org, maybe with a rename to make it clear it's the Eclipse plug-ins.
From: Nathan Ridge <zeratul976@xxxxxxxxxxx>
Sent: Monday, October 29, 2018 2:14 PM
To: Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>; CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Subject: Re: CDT on Github
> Any thoughts for or against?
I don't have any opinion on the location of the repository itself.
However, I wonder: would this affect bug tracking (Bugzilla) or code reviews (Gerrit)? I prefer both of those over their Github equivalents.
cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit