Breezy 2019 summer sprint report

Jelmer Vernooń≥ jelmer at
Sat Sep 7 19:27:12 UTC 2019

On Sat, Sep 07, 2019 at 02:09:08PM +0100, Sam Bull wrote:
> On Sun, 2019-09-01 at 14:08 +0000, Jelmer Vernooń≥ wrote:
> > On Sun, Sep 01, 2019 at 09:26:20AM -0400, Aaron Bentley wrote:
> > > But brz init-repo is documented to create a shared repository ("Create a
> > > shared repository for branches to share storage space.").  If Git doesn't
> > > support shared repositories, I'd expect this to fail.  Possibly it wouldn't
> > > support --git at all.
> > 
> > So to be more precise: a Git repository supports multiple branches in
> > a repository, just *only* colocated.
> Is it infeasible to create a multi-directory approach? I'm not familiar with the
> implementation details, but I just imagined the .git directory contains all the
> data for a Git repo and wouldn't really limit the behaviour of the tool.
> 	So, the .git directory would be in the repo folder, and then when you
> branch it just checkouts the files into a subfolder. Then all the
> status/diff/commit commands would work by comparing the files in the subfolder
> with the data in the parent .git directory for the given branch name.
> If doing this, you'd probably want to rename .git to .brz-git or similar, to
> ensure that the Git program doesn't try to operate on the repo (I don't see any
> real advantage in supporting both programs in the same local repo).

At that point it's no longer a Git repository, and you can't use the
Git command-line tool on it; it seems you want to just use a Bazaar
repository instead if you need to use shared repositories, rather than
adding yet another repository format.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <>

More information about the bazaar mailing list