Keith Mendoza <ke...@icei.org> writes: > Now that development is going to be done on github, what I would > recommend is forking from the official net-snmp and then maybe create > a branch on your github fork.
Why do you think that's better than submitting it as a branch within the offical fork? Just to reduce object growth? > That way github's merge request can be utilized fully. How does that help in this case? I guess it allows commenting on individual changes, but I think the changes are likely too large to be beneficial to that. > We from ICEI (ian, Eric, me) are interested in seeing what you have so > far and maybe we can help pick up from there. One of the problems I know we'll hit is that the patch was done against a much earlier point between 5.7 and 5.8 and there will be conflicts and issues because of it. But I will try to get that branched from hopefully the right point where it still works. -- Wes Hardaker Please mail all replies to net-snmp-coders@lists.sourceforge.net ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
