Comment 2 for bug 251501
Revision history for this message
| Marius Kruger (amanica) wrote Re: Dear Launchpad, please don't add the full text of the bug to the mail when the mail already sends the full text | #2 |
I don't know why Scott says its not a good example, but in any case it happens to me too.
Thanks to this bug report I now know I can disable descriptions in all bug mails, which I did.
Another example:
=======
Public bug reported:
While testing stacked branches, I wanted to skip the working-tree
creation, so I created a shared repo with --no-trees.
When doing so, it created its own standalone repository, rather than re-
using the local one, which also caused it to build a working tree.
I then tried just removing newbranch/
getting failures:
$ time bzr branch stacked/ unstacked --lsprof-file branch_stacked.txt
bzr: ERROR: The branch stacked/ has no revision None.
Which is strange, considering there are 0 pack files in the standalone
location. I certainly would have thought that the standard open commands
would find the shared location.
** Affects: bzr
Importance: Undecided
Status: New
--
stacked branches don't use shared repository
https:/
You received this bug notification because you are subscribed to Bazaar.
Status in Bazaar Version Control System: New
Bug description:
While testing stacked branches, I wanted to skip the working-tree creation, so I created a shared repo with --no-trees.
When doing so, it created its own standalone repository, rather than re-using the local one, which also caused it to build a working tree.
I then tried just removing newbranch/
$ time bzr branch stacked/ unstacked --lsprof-file branch_stacked.txt
bzr: ERROR: The branch stacked/ has no revision None.
Which is strange, considering there are 0 pack files in the standalone location. I certainly would have thought that the standard open commands would find the shared location.