Comments on: New Default Branch Format in Bzr http://blogs.gnome.org/jamesh/2006/04/27/new-default-branch-format-in-bzr/ Random stuff Tue, 17 May 2011 12:23:37 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Olaf Conradi http://blogs.gnome.org/jamesh/2006/04/27/new-default-branch-format-in-bzr/comment-page-1/#comment-153 Olaf Conradi Wed, 30 Nov -0001 00:00:00 +0000 http://blogs.gnome.org/jamesh/2006/04/27/new-default-branch-format-in-bzr/#comment-153 Hi<p/>A minor (k)nitpick :)<p/>Metadir is the bzrdir format to hold tree, branch and/or repository formats.<p/>Your comparison was between the weave and knit repository formats. They both reside in a metadir.<p/>Cheers<br/> -Olaf Hi

A minor (k)nitpick :)

Metadir is the bzrdir format to hold tree, branch and/or repository formats.

Your comparison was between the weave and knit repository formats. They both reside in a metadir.

Cheers
-Olaf

]]> By: James Henstridge http://blogs.gnome.org/jamesh/2006/04/27/new-default-branch-format-in-bzr/comment-page-1/#comment-154 James Henstridge Wed, 30 Nov -0001 00:00:00 +0000 http://blogs.gnome.org/jamesh/2006/04/27/new-default-branch-format-in-bzr/#comment-154 Olaf: I was comparing a repository created with "bzr init-repo --format=metadir" with one created using "bzr init-repo --format=knit". The other value the help mentions is "weave", but that just prints an error stating "Format shared repository is not compatible with .bzr version Bazaar-NG branch, format 6."<p/>I know that both repository types use the metadir bzr dir layout, but I decided to use the terminology used in the command line UI. Olaf: I was comparing a repository created with “bzr init-repo –format=metadir” with one created using “bzr init-repo –format=knit”. The other value the help mentions is “weave”, but that just prints an error stating “Format shared repository is not compatible with .bzr version Bazaar-NG branch, format 6.”

I know that both repository types use the metadir bzr dir layout, but I decided to use the terminology used in the command line UI.

]]> By: Olaf Conradi http://blogs.gnome.org/jamesh/2006/04/27/new-default-branch-format-in-bzr/comment-page-1/#comment-155 Olaf Conradi Wed, 30 Nov -0001 00:00:00 +0000 http://blogs.gnome.org/jamesh/2006/04/27/new-default-branch-format-in-bzr/#comment-155 In latest bzr.dev, the default repository format for metadir changed from weave to knit.<p/>Creating a repository through "bzr init-repo --format=metadir" will create a knit repository. Issuing a "bzr init-repo --format=weave" will create one using weave. The error should actually be a warning, it does create a valid weave repository. In latest bzr.dev, the default repository format for metadir changed from weave to knit.

Creating a repository through “bzr init-repo –format=metadir” will create a knit repository. Issuing a “bzr init-repo –format=weave” will create one using weave. The error should actually be a warning, it does create a valid weave repository.

]]> By: michele http://blogs.gnome.org/jamesh/2006/04/27/new-default-branch-format-in-bzr/comment-page-1/#comment-156 michele Wed, 30 Nov -0001 00:00:00 +0000 http://blogs.gnome.org/jamesh/2006/04/27/new-default-branch-format-in-bzr/#comment-156 Hey guys, it would be nice to upload a egg of bzr 0.8 to the cheese shop [1] once released... so it's easy_installable. ;-) Hey guys, it would be nice to upload a egg of bzr 0.8 to the cheese shop [1] once released… so it’s easy_installable. ;-)

]]> By: wayne http://blogs.gnome.org/jamesh/2006/04/27/new-default-branch-format-in-bzr/comment-page-1/#comment-157 wayne Wed, 30 Nov -0001 00:00:00 +0000 http://blogs.gnome.org/jamesh/2006/04/27/new-default-branch-format-in-bzr/#comment-157 Note that the current development version of bzr has changed the format name of a weave inside a metadir from "metadir" to "metaweave". This new terminology will be included in the 0.8 release. Note that the current development version of bzr has changed the format name of a weave inside a metadir from “metadir” to “metaweave”. This new terminology will be included in the 0.8 release.

]]>