On Tue, May 15, 2018, at 12:58 PM, Wes Hardaker wrote:
> 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, and experience tells me that replacing the build system is one of those 
projects best done in a separate area, if you will. If a "cmake conversion" 
branch is used, I would suggest limiting how often master is merged into this 
branch. That way its easier to figure out where breaking changes occurs. We 
almost have to go back to the old-school way of software development where you 
had a separate "maintenance" team where junior devs were placed--except, let's 
not actually punt it to a bunch of junior devs ;)

> 
> > 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.

If this was done against a known 5.7.x git tag (even one converted from 
CVS/Subversion) it might not be a bad place to complete the conversion from. 
Since it's a well-known point from git's POV git bisect should help in figuring 
out which places it breaks between the conversion and master branch, especially 
with a script that can configure with as many options as possible.

> 
> -- 
> Wes Hardaker
> Please mail all replies to net-snmp-coders@lists.sourceforge.net


-- 
Thanks,
Keith (pantherse)

------------------------------------------------------------------------------
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

Reply via email to