On Aug 25, 2015, at 10:21 PM, Carl Swanson wrote:

> Does anyone work on a large nodejs project with a decent sized team where 
> code source branching problems and re-merging becomes a problem? Where 
> multiple people touch the same relative code area, and then have effort 
> needed on successive check ins to merge code back together?
> 
> What have you done to solve this type of issues?
> 
> I'm doing some research and would love to hear from ideas in this area.

Could you elaborate on why this would be a more acute problem with nodejs-based 
JavaScript code than it would be with other kind of code?


-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/F4BB7276-AB32-438A-AC62-A68E1DD7E171%40ryandesign.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to