{"thread":{"id":"3014","subject":"Re: git pull on Linux/ACPI release tree","startedAt":"2006-01-09T05:55:42Z","lastAt":"2006-01-09T05:55:42Z","messageCount":1,"participants":["linux@horizon.com"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"14339","messageId":"20060109055542.20320.qmail@science.horizon.com","threadId":"3014","inReplyTo":null,"subject":"Re: git pull on Linux/ACPI release tree","fromName":"","fromEmail":"linux@horizon.com","sentAt":"2006-01-09T05:55:42Z","receivedAt":"2006-01-09T05:55:42Z","isPatch":false,"sender":{"key":"linux@horizon.com","avatar":null},"body":"> And lastly, is there a tool whereby I can \"see\" changes\n> between repos, kind of like git-diff but being able to\n> give URLs too?\n\nWrite it yourself.  It's git-fetch + git-diff.\n\nOr, put another way, if you think you need a special tool for working\nwith a remote repository, you don't understand git-fetch.\n\nSince git history is immutable, there is no difference between a remote\ncopy and a local copy.  And since fetching is harmless to your local\nrepository, there's no problem.\n\nIf you don't want to copy the entire history, just fetch the tree rather\nthan the commit.  (Does git-fetch do that?  It's a subset of its current\neffects, so would be an easy enough extension.)\n"}]}