On Tue, Mar 16, 2010 at 09:54:28PM +0300, Pavel Emelyanov wrote: > On 03/16/2010 08:57 PM, maximilian attems wrote: > > On Tue, Mar 16, 2010 at 08:31:31PM +0300, Pavel Emelyanov wrote: > >>> > >>> a build with all of those option turned off. > >>> can retest easily. > >> > >> Hm... Mine compiles just fine. > > > > cool, good news. > > > >>> we are uploading today 2.6.32.10 to unstable, > >>> I'd like to include openvz, sorry for short notice, > >>> but as you didn't rebase on top of 2.6.32.10 i have > >>> trouble to extract the openvz patch for debian which > >>> should be just on top of that, my git foo don't tells > >>> me how to exclude the merged 2.6.32.10 > >> > >> I've pulled it 6 hours ago. Re-check the git. > > > > yes i've seen but the way it is I don't know how to extract > > a plain patch of it that has just openvz on top of 2.6.32.10 > > previously i would do > > git log 7f5e918e62cbc9ac27c2f47d3c3dd4b86f67ff0e.. > /tmp/openvz > > git diff 7f5e918e62cbc9ac27c2f47d3c3dd4b86f67ff0e.. >> /tmp/openvz > > Hm... I'd think that > $ git diff v2.6.32..HEAD > made in the repo's master should work :\
this seems to do the trick, don't know whats special about three dots: git diff v2.6.32.10...HEAD will give it a spin. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
