Hi, I hesitate to post this to the public list since it's significantly off-topic, but...
I'm looking at maintaining some merged kernel patches from a variety of projects and looking at using git to do so. If you don't mind me asking, can you briefly describe how you use git to maintain aufs and any gotchas/tips you have discovered while using git for this? What I *think* you have done is forked the linux kernel, then you develop in your favourite kernel branch (.37 or whatever), and finally there is some magic going on to merge your changes with upstream and other branches? What I think you must be doing is a "git cherry-pick" to grab the individual commits from the upstream kernel branch? Then I guess you are checking out all the individual kernel tree versions and merging the aufs changes from your development branch - however, that's showing up as a merge rather than a cherry-pick, so slightly curious what your workflow is there also? Basically mostly interested in how you track the upstream kernel commits (presumed to be a cherry-pick?) and any tips you have learned to do this efficiently? Thanks Ed W ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb
