aboutsummaryrefslogtreecommitdiffstats
path: root/.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/12c986be-d19a-4b8b-b1b5-68248ff4d331/comments/e520239c-8d69-4ff6-b1bd-0c2f74366200/body
blob: 0263fbb57bc222917f9ed390c8445ade42aa261f (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
Ronny Pfannschmidt <Ronny.Pfannschmidt@gmx.de> writes:

> i want to see the combination of the bug data of all branches

What is your definition of “all branches”? When I'm working with
distributed VCS, I create branches wherever I feel like, and the VCS
tool doesn't have some central registry of branches to keep up to date.

How is a tool to determine the set of “all branches”? The distributed
VCS model means that set is indeterminate.

-- 
 \         “Pinky, are you pondering what I'm pondering?” “I think so, |
  `\    Brain, but I find scratching just makes it worse.” —_Pinky and |
_o__)                                                       The Brain_ |
Ben Finney


_______________________________________________
Be-devel mailing list
Be-devel@bugseverywhere.org
http://void.printf.net/cgi-bin/mailman/listinfo/be-devel