don't open repository unless/until needed
Bug #112028 reported by
Alexander Belchenko
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Several commands of bzr that works only with working tree object or branch object, like status, add, remove, tag(s), may be some others? -- should not open repository at all. We need some sort of lazy open for repository. Open repository every time just waste of time without any real needs to read data from repository.
My real use case (despite performance question): sometimes I move old branches away from shared repository to "limbo" folder. This limbo is not a subdirectory of shared repo, usually it at level up. After I move my branch I cannot do 'bzr st' just for simple check before I completely remove data from limbo.
tags: | added: check-for-breezy |
To post a comment you must log in.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alexander Belchenko wrote:
> Public bug reported:
>
> Several commands of bzr that works only with working tree object or
> branch object, like status, add, remove, tag(s), may be some others? --
> should not open repository at all. We need some sort of lazy open for
> repository. Open repository every time just waste of time without any
> real needs to read data from repository.
But
- most commands do need the repository
- a lazy-open approach introduces new failure modes for dubious gain
- you have produced malformed trees by moving them outside the repo,
and it's fine for bzr to fail on malformed trees.
Aaron enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFGOeHn0F+ nu1YWqI0RArC0AJ 9rXlarHq7zDvHiB dh+6t0tn3b1jwCf codA QCCHMyKk=
A/38IY1nwUfZAmQ
=skbi
-----END PGP SIGNATURE-----