Julian Andres Klode: > > $ git checkout aufs2-xx # for instance, aufs2-27 for linux-2.6.27 > This has to be: > git checkout -b aufs2-xx origin/aufs2-xx
I see. And I also confirmed "git checkout origin/aufs2-xx" worked. Thank you. > BTW, I would have preferred standalone branches with normal commit > messages, but if you think that your solution is better OK. I just don't know how to do it. I committed aufs2-2.6.git first and then built aufs2-standalone.git by git-diff and git-log under aufs2-2.6.git. If you know better way, let me know please. > I also don't understand why you have the aufs2 aufs2-stdalone* branches > in aufs2-2.6.git. And I don't understand why your master is the upstream > kernel, and not your patched one (as master normally indicates the=20 > current state of development). Yes, the aufs2-stdalone* branches in aufs2-2.6.git are unnecessary. Actually I tried to delete them by "git branch -r -d". But it didn't work as I expected. The branches are left still. About the aufs2 branch, the git manual told me that I should not commit to the master branch if I make "pull request" to mainline in the future. > Furthermore, it would have been better to have a location which supports > the git protocol, because cloning over http is really slow. Really? I didn't know that either. I have not felt http is slow myself. But if many people feel so, I may find another public GIT tree again. > And I don't understand why you have all these 'test' commits. They are=20 > just useless. I made git-rm and git-push now. J. R. Okajima ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H
