On Fri, Jun 04, 2010 at 05:01:18PM +0200, Gianluca Montecchi wrote: > Nothing except that you need to have all the branches downloaded to > different directories.
"branches" gets a bit murky across our range of DCVSs. Different directories are not so much of a hassle, and it will make BE much faster, since direct filesystem access is a lot faster than filesystem-via-a-VCS. > And still you don't have a unique list but just some lists of bugs that you > need to merge in some way. On Fri, Jun 04, 2010 at 04:27:31PM +0200, Ronny Pfannschmidt wrote: > but i want to have some kind of central access to the bug database > for end-users and maintainers If someone can give a clear description of the desired interface, one of us will code it up sooner or later. Suggested interface: be list -r repo1,repo2,repo3,repo4 which is not currently implemented, but would be pretty easy. As well as be show -r repo1,repo2,repo3,repo4 ID which would show the bug exactly like be show -r repo1 ID except that Status : <repo1 status> would become Status : <repo1>:<repo1 status>, <repo2>:<repo2 status>, ... If ID was not present in repo1, repeat with repo2,repo3,repo4. I doubt you really care about the other fields, but the same approach would work there too. Obviously we'd make equivalent changes to `be html` and CFBE. This is basically just a slicker wrapper around my suggestion in bea/12c/624. -- This email may be signed or encrypted with GPG (http://www.gnupg.org). The GPG signature (if present) will be attached as 'signature.asc'. For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt
pgpomxK08eJN1.pgp
Description: PGP signature
_______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
