On Sat, Jan 26 2008, Stefan Reichör (SR) and Michael Olson (MO) wrote: SR> The first important point for contributions is, that you must sign SR> Emacs papers. I guess that you are willing to do that. Michael Olson SR> will provide the details for this process.
MO> Another thing to keep in mind is that if your patches cumulatively MO> change more than 15 or so lines, we'll need you to fill out a copyright MO> assignment form for the FSF. Email me off-list if you want to get that MO> out of the way. Okay, no problem. I'll sort this out with Mr. Olson. SR> I prefer one branch for every active contributor. I have set up SR> bookmarks list. This setup makes merging very easy. So when you are SR> planning to help us improving DVC, it is best that you create your own SR> branch. I will merge your changes. MO> A public bzr branch would be much easier. Just be sure to set up MO> `bzr-mail-notification-destination'. Then when you make a change, bring MO> up the log buffer, and hit "M" on an entry to send us a notification MO> about it. Okay, I'll do that. I'll probably use Launchpad to host it. MO> DVC's Gnus integration actually doesn't seem to support "bzr send" yet. MO> (A patch to implement support for it might be nice.) We do support MO> patches sent via "M-x dvc-submit-patch RET", however. dvc-submit-patch requires that the changes be uncommitted, correct? Regards, Toby. _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
