Toby Allsopp <[EMAIL PROTECTED]> writes: > [Apologies if this turns up twice; I initially posted it to Gmane but > it hasn't shown up.] > > Hello, DVC developers. > > I'm hoping to offer some improvements to DVC, starting with simple > build fixes and hopefully moving on to adding features (e.g. bzr send > support). I'm wondering how best to submit patches. > > I have already sent one patch using `bzr send' and I see that it was > promptly applied, so that seems to work pretty well.
DVC's Gnus integration actually doesn't seem to support "bzr send" yet.
(A patch to implement support for it might be nice.) We do support
patches sent via "M-x dvc-submit-patch RET", however.
> An alternative is for me to make one (or more) bzr branches publicly
> accessible and ask the list to consider merging from them.
>
> What would be easiest for the developers?
A public bzr branch would be much easier. Just be sure to set up
`bzr-mail-notification-destination'. Then when you make a change, bring
up the log buffer, and hit "M" on an entry to send us a notification
about it.
Another thing to keep in mind is that if your patches cumulatively
change more than 15 or so lines, we'll need you to fill out a copyright
assignment form for the FSF. Email me off-list if you want to get that
out of the way.
--
Michael Olson -- FSF Associate Member #652 |
http://mwolson.org/ -- Jabber: mwolson_at_hcoop.net | /` |\ | | |
Programmer -- Hobbies: Lisp, HCoop | |_] | \| |_|
Projects: Emacs, Muse, ERC, EMMS, ErBot, DVC, Planner |
pgpcs2DU8q0AL.pgp
Description: PGP signature
_______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
