On Sat, 23 Apr 2005, Petr Baudis wrote: > Dear diary, on Fri, Apr 22, 2005 at 09:46:35PM CEST, I got a letter > where Daniel Barkalow <barkalow@iabervon.org> told me that... > > Huh. Why? You just go back to history until you find a commit you > already have. If you did it the way as Tony described, if you have that > commit, you can be sure that you have everything it depends on too. But if you download 1000 files of the 1010 you need, and then your network goes down, you will need to download those 1000 again when it comes back, because you can't save them unless you have the full history. There's also no way to say, give me just the head and the tree associated with it, let me check it out, next download the commit history so I can do my merge most correctly, let me do that, finally download the intermediate blobs and trees so that I can track down where something broke. Ideally, you'd be able to put the latest head and tree into your database, and it would know that you just hadn't gotten the ancestor yet, and would be able to determine from your personal metadata (rather than based on what you had or lacked) that you believe you have all ancestors of the previous time you pulled, you don't want the trees that Linus merged in midway through, but everything else you just don't have yet. -Daniel *This .sig left intentionally blank* - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Sat Apr 23 09:01:01 2005
This archive was generated by hypermail 2.1.8 : 2005-04-23 09:01:01 EST