How can we ensure Bazaar (bzr) remains active?
Eli Zaretskii
eliz at gnu.org
Tue Sep 22 06:33:09 UTC 2015
> Date: Tue, 22 Sep 2015 18:25:09 +1200
> From: Robert Collins <robertc at robertcollins.net>
> Cc: Jelmer Vernooij <jelmer at jelmer.uk>, Bazaar <bazaar at lists.canonical.com>,
> bronger at physik.rwth-aachen.de
>
> On 22 September 2015 at 18:19, Eli Zaretskii <eliz at gnu.org> wrote:
> >> Date: Tue, 22 Sep 2015 00:51:08 +0000
> >> From: Jelmer Vernooij <jelmer at jelmer.uk>
> >> Cc: Torsten Bronger <bronger at physik.rwth-aachen.de>,
> >> bazaar at lists.canonical.com
> >>
> >> bzr-git is slow because it has to do format conversion - it can't
> >> simply copy the pack file like "plain" Dulwich and C Git can. bzr-git
> >> fetches from a Git format repository into a Bazaar format repository.
> >>
> >> This means that when bzr-git fetches it has to recreate every Git
> >> fulltext by applying the Git delta chain to create that fulltext, and
> >> then insert it into the Bazaar repository (which involves generating
> >> a pack filled with deltas in Bazaar's format).
> >
> > My reading of this is that having a bzr-like UI that uses bzr-git as
> > back-end is a non-starter to begin with.
>
> Actually its in-principle possible to generate bzr format compressed
> texts directly from git ones: it wouldn't be as compressed, but its a
> fairly trivial transform.
But then it won't be bzr-git, it will be something else, right?
I was talking only about bzr-git as the engine behind this idea.
More information about the bazaar
mailing list