Re: any plans on suporting subrepos/submodules/nested trees as a mean to share bugs across the boundaries of branches?
W. Trevor King <wking <at> drexel.edu>
2010-06-04 16:53:53 GMT
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
> 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
Status : <repo1 status>
Status : <repo1>:<repo1 status>, <repo2>:<repo2 status>, ...