On Fri, 1 Jul 2005, H. Peter Anvin wrote: > > It's a log. ..but that's not what we're looking for. I'm not looking for kernel.org to be my distributed backup tape. For it to be useful, it must do more than just log all activity and mirror it out via rsync. It must also be usable for people pulling on it. Which means that it has to be a valid git archive or at least easily incrementally unpackable, so that people can actually use the end result. A log of packs that are just incremented is certainly unpackable: you teach git-unpack-objects to just unpack several packs after each other. But since it's not seekable, you'd have to unpack a 100MB compressed archive just to get the last tip of it that you don't have unpacked yet. Also, it means that it's impossible to efficiently do a git-specific thing. I want people to be able to do what we used to be able to do with BK: just do a git pull master.kernel.org:xxxx and get something useful. And that means _not_ having to pull a 100MB blob to get the last objects at the end. And don't tell me "rsync can efficiently get just the end". That's true for _mirrors_, but it's not true for users that don't have every single archive on kernel.org. I don't have (and I don't want to have) a copy of every single persons log that ever might want to push to me. So no, a log simply isn't useful. It _has_ to be a valid git archive to be useful. Thousands of objects satisfy that. Or a "few packs + few objects". Not a log. Linus - 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 Jul 09 17:33:28 2005
This archive was generated by hypermail 2.1.8 : 2005-07-09 17:33:30 EST