2008/11/5 Nick Coghlan <[EMAIL PROTECTED]>: > Paul Moore wrote: >> While that would be good, my understanding is that stacked branches in >> Bazaar only work (for history operations) while you're online. So they >> make Bazaar work a little like a centralised VCS, I guess. Not sure >> how that's a step forward :-) > > You only need full history in order to ask "how did this code get to > this state" type questions. That's something a core dev will > occasionally want to know (which is why we would take to the time to > setup a full checkout no matter how long it takes), but utterly > irrelevant to a casual committer such as the one in your "write and > submit a quick patch" scenario.
Agreed. But I'm very hazy on how Bazaar stacked branches work in practice. If I create a nice fast stacked branch on my PC, then go offline, precisely what operations can I no longer do? And will the ones that can't work fully, work "for the first bit" (by which I mean something like bzr log | less, exiting before I page through the lot - that's my normal history search process, because my poor brain is too slow to remember the flags to limit the history :-))? Anyway, this is probably getting too much into details to be useful. Paul. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
