4 ms·

> There may have been outside discussions and real issues that made merging a bad idea Yeah, and Eric Brewer got on stage at DockerCon June and stated that pre

• 23david 12y ago
  Part of the problem here could definitely be communication. For whatever reason, it's been incredibly hard to follow what is going on with the Docker project. Keeping info in one place would definitely help. I'm not able to find any details that support what you're saying. It seems that in June Eric Brewer was still publicly asking for libcontainer to merge in LMCTFY support. I definitely could be wrong, but looking at this screenshot from Eric's June talk it looks like they were still trying to get it merged: https://pbs.twimg.com/media/B4DKb51CYAA687s.jpg:large https://pbs.twimg.com/media/B4DKb51CYAA687s.jpg:large In June, Eric Brewer posted this: We’ve released an open-source tool called cAdvisor that enables fine-grain statistics on resource usage for containers. It tracks both instantaneous and historical stats for a wide variety of resources, handles nested containers, and supports both LMCTFY and Docker’s libcontainer. It’s written in Go with the hope that we can move some of these tools into libcontainer directly if people find them useful (as we have). http://googlecloudplatform.blogspot.com/2014/06/an-update-on-container-support-on-google-cloud-platform.html http://googlecloudplatform.blogspot.com/2014/06/an-update-on...
• Alupis 12y ago
  If this happened, it would be normal and expected for that to be noted on the PR/Issue Ticket. How can you expect someone say 6 months - 1 year from now to know this unless it's clearly documented? That is what the Issues system is for.