Some of you have already seen my patches at https://defect.opensolaris.org/bz/show_bug.cgi?id=15961 and been giving helpful feedback, and I thank you for it. I wanted to extend a big thank you for writing OpenGrok, too. All the developers I work with love it--it's so much nicer than the similar Lucene-based code search tool we wrote in-house many years ago.
I'm wondering if submitting patches to the defect tracker is really the preferred development method, as I am realizing that my patch has several parts which can be applied independently. I am happy to split it up into symlink support, clearcase isRepositoryFor improvments, and automatically indexing symlinks that are in source root. I can attach them all to the existing defect, create new ones for each patch, give direct access to my mercurial repo (which might be tricky because I'm behind a pretty restrictive firewall). What does the development team prefer? I have a good idea of how to split the patch up using git, but I'm new to mercurial. Are there any suggestions? Perhaps the MQ extension? Thanks, Patrick -- This message posted from opensolaris.org _______________________________________________ opengrok-discuss mailing list opengrok-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss
