I've noticed people trying to send patches to BBDB 3.x via this
mailing list. One potentially more convenient alternative you be to
use git's facilities for this purpose. In particular, I'm keeping a
copy of the savannah "central" BBDB 3.x repository at
github.com/barak/bbdb3 which also contains debian packaging
information.
A straightforward work flow for patches would be to make yourself a
github.com account, "fork" the above repository on github so you have
your own copy, push your patches to your forked repository on github,
and then either wait (I'll see them) or send a "pull request" that
I'll see. Then I'll pull your patches, probably to a branch
"yourname-patches" rebased on Roland's current tip, and then he can
pull them into the savannah repository as appropriate. (Modulo
technical and paperwork issues.)
Since the BBDB 2.x CVS repository is effectively dead, patches to BBDB
2.x can be made similarly by forking the repository
github.com/barak/BBDB and issuing a pull request.
--Barak.
--
Barak A. Pearlmutter
Hamilton Institute & Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
http://www.bcl.hamilton.ie/~barak/
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/
