On Fri, Feb 08, 2013 at 11:36:48AM -0700, Marguerite Su wrote: > > > > On Wed, Feb 6, 2013 at 11:15 PM, Josef Bacik <jbacik@xxxxxxxxxxxx<mailto:jbacik@xxxxxxxxxxxx>> wrote: > > Btrfs-next is based on 3.7, you should be able to just git diff v3.7.. > > whatever.patch and get all the changes you need. Thanks, > > Hi, Josef, > > Sorry to bother you again. I tried for days and asked some of my friends, but I'm still confused about what you want me to do and how to do... > > I check the #btrfs-next[1], its latest tag is v3.4-rc2 and there's only one master branch. There's no `v3.7` around there...So I'm confused about what you meant. Can you be more detailed ? > > I know I need a diff...but how...and which repo should I apply it on? my /usr/src/linux or #btrfs-next itself? > > Thanks a lot > Oh sorry I have the tags locally because I pull linus's tags onto my tree, but I don't push them out. So pull my tree (I just pushed another fix for this problem out yesterday so it definitely should be fixed) and just do git diff 29594404d7fe73cd80eaa4ee8c43dcc53970c60e.. > btrfs.patch and that should work. Thanks, Josef -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
