<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7650.21"> <TITLE>R: Revision-id of the bazaar version</TITLE> </HEAD> <BODY>  Hi all, I understand the point: the stables releases can diverge from the devel releases. In general they are different branches. And the branch can happen before the release of the ufficial revision. Ok, but I think that it should be an official repository with the stable branches, and a list of the revision-id(s) for every version. Goffredo -----Messaggio originale----- Da: John Arbash Meinel [<A HREF="mailto:john@arbash-meinel.com">mailto:john@arbash-meinel.com</A>] Inviato: lun 23/10/2006 11.41 A: kreijack@alice.it Cc: bazaar-ng@lists.canonical.com Oggetto: Re: Revision-id of the bazaar version -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Goffredo Baroncelli wrote: > Hi all, > > is there an official list of the revision-id for every version of bazaar ? > > > Looking at the NEWS annotate it seems: > Well, these can't be the official revision ids, because *most* of the actual releases were not merged back into the mainline. Robert has explicitly asked for this, because it prevents you from accidentally doing a pull overtop of the released branch. As an example:  A  |  B  |\  C E - release-0.8  |  D  |  F  |\  G H - release-0.9 etc. The problem is that if you do:  F  |\  G H  |/  I Then if you are sitting at 'H' and accidentally do 'bzr pull', it will give you I, which is *not* on the release branch. Personally, I could see going either way. I like the concept that if I pull bzr.dev, I get all of the history, even for releases. This is also a place were I think tags would make sense. (tags such that they propagate with the branch, but are difficult to change). I maintain a mirror for all of the released versions that I've found. Which doesn't contain some of the older ones. Most of these can also be found on <A HREF="http://bazaar-vcs.org/bzr/">http://bazaar-vcs.org/bzr/</A> bzr.0.0.5 mbp@sourcefrog.net-20050615060316-97b948fb1eade31f bzr.0.1   mbp@sourcefrog.net-20051013032322-dc469f4b81f8e7f9 bzr.0.6   mbp@sourcefrog.net-20051028055627-b80f0d7d43d07407 bzr-0.7-fixes mbp@sourcefrog.net-20060120051910-199f6d5e9d1e5c6d bzr.0.8   pqm@pqm.ubuntu.com-20060517071027-58ef74796b918716 bzr.0.9   pqm@pqm.ubuntu.com-20060811102108-06a24f3a1d4e7d82 bzr.0.10  pqm@pqm.ubuntu.com-20060904005919-d595cc974f859400 bzr.0.11  pqm@pqm.ubuntu.com-20061001233254-c3a627b7c1390697 Now, I personally merged the 0.10 branch back into bzr.dev, but I don't believe the other ones have been merged. My mirrors are available from: <A HREF="http://bzr.arbash-meinel.com/mirrors/bzr/releases/">http://bzr.arbash-meinel.com/mirrors/bzr/releases/</A> (I think I tweezed out bzr.0.0.5 and some of the others by looking through commit logs and seeing 'prepare 0.X release'. So they may not be 100% accurate) John =:-> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) Comment: Using GnuPG with Mozilla - <A HREF="http://enigmail.mozdev.org">http://enigmail.mozdev.org</A> iD8DBQFFPI40JdeBCYSNAAMRAsxiAJ90oxMshz2IN46Vh8nARzWZfiGyEQCg1wKh phw8IBH6N4yPWyg4nhBMkO0= =0XA7 -----END PGP SIGNATURE----- </BODY> </HTML>