On Fri, 22 Aug 2008, Andi Kleen wrote: > > Well git fetch does nothing by itself. Git fetch does exactly what it should do by itself. If you think it does "nothing", you're really confused. It updates the "remote" branches - the ones you are downlaoding. > Sorry that's what I though initially too. But that's wrong. Just clone > e.g. linux-next and then try to update it with pull a day later. You SHOULD NOT DO THAT! linux-next is not a tree that you can track. It's a tree that you can fetch _once_ and then throw away. So what you can do is to "fetch" linux-next, and test it. But you MUST NEVER EVER use it for anything else. You can't do development on it, you cannot rebase onto it, you can't do _anything_ with it. So what you can do is to "git fetch" it (to download it), and then "git checkout" to create a temporary checkout. That's pretty much all you can do with linux-next. > rebase messed this all up majorly. And people use that unfortunately. Exactly. Don't rebase. And don't base your development on somebody who does. And "linux-next" is literally just a temporary tree that is a merge of a lot of random trees. It has no future. Remember how I told you that you should never rebase? Linus -- 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
