On Thu, 2004-07-22 at 06:34, Carsten Lohrke wrote: > I never assumed to write xml by hand - Stuarts email sound a bit like it - but > even "field1", "field2", ... would be annoying. If echangelog > would be smart and parse the input, that would be ok. Maybe I got it wrong, > but I was under the impression that there would be at least one new field be > introduced, indicating the importance of a bug fix; And a increasing number > of fields wouldn't make parsing input simpler. If using xml doesn't > complicate writing the ChangeLog I'm all for it. What about something like: echangelog Then you make echangelog a bit smart. You could use it in several ways. echangelog "text here" for changes that are made without a bug attached or any additional information. echangelog "text here" "69" for changes that are made to close bug #69. But what if you want to enter but not a bug? Then you would use echangelog "text here" "" "foo" (just an idea). All of this would keep echangelog from getting too complex, while still giving it flexibility. Any better ideas are definitely welcome... =] -- Chris Gianelloni Release Engineering QA Manager/Games Developer Gentoo Linux Is your power animal a penguin?