{"thread":{"id":"10259","subject":"Re: git branch performance problem?","startedAt":"2007-10-12T17:32:22Z","lastAt":"2007-10-12T17:32:22Z","messageCount":1,"participants":["Salikh Zakirov"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"55567","messageId":"20071012173221.GA5475@makoto.usen.ad.jp","threadId":"10259","inReplyTo":null,"subject":"Re: git branch performance problem?","fromName":"Salikh Zakirov","fromEmail":"salikh.zakirov@gmail.com","sentAt":"2007-10-12T17:32:22Z","receivedAt":"2007-10-12T17:32:22Z","isPatch":false,"sender":{"key":"salikh.zakirov@gmail.com","avatar":null},"body":"Han-Wen Nienhuys wrote:\n> For cherrypicking convenience, I would still appreciate it if there\n> was a mechanism similar to alternates that would allow me to view\n> objects from an alternate repo; objects found through this mechanism\n> should never be assumed to be present in the database, of course.\n\nThere exist a script contrib/workdir/git-new-workdir,\nwhich creates a new working copy that literally shares the same object store.\nIt will share both object store and branches, so some care must be taken:\nbranch which checkout out in one shared working directory must never be\nupdated\n(committed or pulled into) from the other shared working directory.\n\nSaid that, I personally find this trick very useful for browsing code \nfrom different branch and quick bug fixing.\n"}]}