On Fri, 08 Aug 2014 13:04:15 -0400, Nick Krause said: > 1.git branch next No, this should be (3) or so. You really want to 'git clone' linus's tree and then 'git remote add' the linux-next tree before you do this. If you're new to git, do yourself a favor, follow the directions, and just build and then boot an updated linux-next kernel every day for a week or so, just so you know you haven't dorked up your base, *before* you go adding more branches of your own. And you'll do yourself a favor by calling the branch 'nickswork' or something so you don't confuse it with a -next branch down the road. If you're planning to go on another scattershot ramble across the kernel like before, you *really* want to put each set of patches on a separate topic branch so you can switch to that branch and 'git diff' will then only produce a diff that contains the 2-3 patches in that topic.
Attachment:
pgphEdghGVuDp.pgp
Description: PGP signature
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
