> Is it possible then to see our 400 odd commits then in the Local > branch on top of 2.6.17 so that we can see not only our history but > also the history that came before? Then as Master advances we can see > about backporting and bringing our code close enough to mainline > kernel to actually be able to contribute back to the community and > submit patches. Is this realistic approach. I am unsure of the GIT > commands that I need to do this? Yes. There are two ways to do this: 1) Use the grafts feature. You can put a line in your repository's .git/info/grafts which lists your initial commit and the ancestors you want it to have. E.g. note that Linus's v2.6.17 is 427abfa28afedffadfca9dd8b067eb6d36bac53f, with parent ce221982e0bef039d7047b0f667bb414efece5af. So you can just include <your initial checkin> ce221982e0bef039d7047b0f667bb414efece5af in git/info/grafts, and boom. The advantage is that you don't have to change anything. The disadvantge here is that this is NOT automatically propagated by pull operations (it would be a security breach if it were), so everyone pulling from you has to do the same thing manually. (If you're only sending out patches, it doesn't matter as much.) 2) Rebase your changes. Import a standard Linux kernel into the repository, and rebase your changes from your original root import onto Linus' 2.6.17. The advantage here is that the commit IDs will be preserved when you share your changes, so if you have your changes pulled into the kernel mainline, it'll be easier to merge them and for you to merge back. The disadvantage is that everyone who has cloned from you has to manually re-fetch once. Basically, option 1 has less immediate pain, but has an ongoing cost. Option 2 gets it out of the way all at once. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
