aboutsummaryrefslogtreecommitdiffstats
path: root/.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/2f048ac5-5564-4b34-b7f9-605357267ed2/comments/074ef29a-3f1d-46dc-8561-7a56af7e6d67/body
blob: 5ce4f1c98ce827f98aae0adde0800fb6c7e2d6c4 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
"W. Trevor King" <wking@drexel.edu> writes:

> On Sat, Jul 04, 2009 at 10:19:35AM +1000, Ben Finney wrote:
> > Instead of a separate command for each output format, could we have
> > a single "produce a static report of the bug database" command, and
> > specify output format as an option?
> > […]
> 
> Do people like this architecture better than my be-xml-to-mbox
> approach?

I think this question is illuminated by the related question: Is mbox
output a static report, or another read-write data store?

It can technically be both, of course, which is why the question may be
helpful: it may help show what is the *conceptual* purpose of the mbox
output format for Bugs Everywhere.

-- 
 \         “Time is the great legalizer, even in the field of morals.” |
  `\                                                 —Henry L. Mencken |
_o__)                                                                  |
Ben Finney