On Wed, Jun 11, 2008 at 03:57:49PM +0200, Adam Hamsik wrote: > *** Please keep me on CC when you replying from dm-devel list I'm not > currently subscribed there. *** > I have created patch against latest release of libdevmapper, it would > be great if we will be able to manage > commiting of this patch to libdevmapper main repo. My patch is > currently not ready to commit, it needs major cleanup, but I thought > that it would be good to let dm developers know about my effort and > show my work to them. We'd be happy to include such patches in the userspace tools and libraries. Just ensure that all the differences are abstracted suitably so that 'configure' can deal with them without breaking linux:-) Note that we're part way through the process of merging the device-mapper and lvm2 source trees: when this is complete releases will consist of a single tarball with a single 'configure.in' (and an option just to build the former device-mapper components). Rather than sending one patch at the end, it's probably better to send smaller patches as you go along, as and when logically-coherent sets of changes are ready. Also, try to avoid copying and pasting code into new files where very little is changing - create internal library functions or include files and share them instead, refactoring existing code as required. Alasdair -- agk@xxxxxxxxxx -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
