On Sun, 2006-10-22 at 22:06 +0200, Jakub Narebski wrote: > David Clymer wrote: > > 1. revnos don't work because they don't serve the same purpose as revids > > or git's SHA1 commit ids. > Revnos works only locally, or in star-topology configuration. They have > some consequences: treating first parent specially, need for merges > instead of fast-forward even if fast-forward would be applicable, > two different "fetch" operators: "pull" (which uses revids on the > pulled side) and "merge" (which preserves revids on pullee side). s/revids/revnos/g but yes, I think I said this later in my previous email. > > > 2. bzr does not support fully distributed development because revnos > > "don't work" as stated in #1. > Bazaar is biased towards centralized/star-topology development if we > want to use revids. In fully distributed configuration there is no > "simple namespace". So revnos aren't globally meaningful in fully distributed settings. So what? I don't see how this translates into bias. There is a lot of functionality provided by bazaar that doesn't really apply to my use case, but it doesn't mean that it is indicative of some bias in bazaar. > > > 3. Ok, bzr does support distributed development, I just say it doesn't > > because I think revids are ugly. > I think that bzr revids are uglier that git commit-ids. > > If on the pros side of bzr is "simple namespace", you must remember that > it is simple namespace only for not fully distributed development. The > pros of "simple namespace" with cons of "merge" vs "pull" and centralization > required for uniqueness of revids. I think you've switched revids and revnos, but I get what you are saying. In fact, I think I said pretty much the same thing in the email you are replying to. I don't think that anyone is disagreeing about anything other than the assertion that bzr is biased because revnos are used to simplify cases where it is possible to do so. In any case, Matthew Fuller & Carl Worth cover this in greater detail in emails further down in this thread (or one of its siblings), so I think I'll stop here. -davidc -- gpg-key: http://www.zettazebra.com/files/key.gpg
Attachment:
signature.asc
Description: This is a digitally signed message part