Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Brendan Miller <catphive@ca...> - 2011-12-01 23:25:30
I know that cedet merges with emacs periodically. If I have a patch to
submit to cedet, do I need to provide copyright assignment to the GNU
I'm not very familiar with bzr. Is there best way to contribute
changes to email this list with a patch, or is there some software to
send a pull request similar to how things are done on github?
From: David Engster <deng@ra...> - 2011-12-02 16:15:36
Brendan Miller writes:
> I know that cedet merges with emacs periodically.
Well, that's the plan. ;-)
> If I have a patch to submit to cedet, do I need to provide copyright
> assignment to the GNU project first?
Yes, if it is longer than ~15 lines of code or text.
> I'm not very familiar with bzr. Is there best way to contribute
> changes to email this list with a patch, or is there some software to
> send a pull request similar to how things are done on github?
For smaller changes, it is probably easiest to simply send a patch to
the list. Please provide a proper ChangeLog entry, and please do not
just copy&paste the patch, since this will usually get garbled by the
involved MUAs; just attach the patch separately to your mail instead.
For larger changes, it makes sense to work on a separate "task branch"
where you can commit frequently (please use proper log entries), which
will also make it easier for us to understand your changes. See the file
USING_CEDET_FROM_BZR for an introduction to those task branches. You can
then either publish that branch, or generate a 'bundle' and send it to
There's also the command 'bzr send', but I've never used it and don't
know how well it works.