...and if you've forked Tracks into your own tracks repo on github and need to reparent that to TracksApp/tracks, the answer should be to make a similar change to the upstream URL, as per http://help.github.com/fork-a-repo/
Both URLs are just entries in .git/config in the project directory, so you could just edit that file with a text editor and change the URLs that way. Fundamentally, Git doesn't care much about where it pulls from—it just looks up the URL in the config, goes there, and downloads all the objects with hashes it doesn't already have. Since the hashes are based on content, the historical trunk ones will be the same whichever upstream Tracks repo you were using, so it should just be a matter of changing where Git goes to get updates or upstream updates. I found <http://newartisans.com/2008/04/git-from-the-bottom-up/> very helpful when getting to grips with it. mathew _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
