On Fri, 2004-07-23 at 10:18, Carsten Lohrke wrote:
> > echangelog <text> <bug> <foo> <bar>
> 
> These are fields, separated by spaces, too. What about when I type (take in 
> account my second nick name is typo):
> 
> echangelog had to touch this <beeep> ebuild the 4 th time because of 
> continuing problems with bug 0815 and 4711 - thanks to joe helpful et al
> 
> How does echangelog know which of these numbers refer to bug reports?

Actually, it would throw an error to begin with since you're not using
the desired input format.

You would need to input something like:

echangelog "had to touch this <beeep> ebuild the 4 th time because of
continuing problems with bug 0815 and 4711" "815 4711" "joe helpful"

It would take the bugs from the "bugs" field.  It shouldn't parse the
text field at all.  That's the whole point that I think everyone is
trying to make with xml'izing the ChangeLog.  Instead, you would do
something more like this:

echangelog "Modified src_unpack to add the fix-bug-0815.patch and also
the fix-bug-4711.patch to the ebuild" "815 4711" "Joe Helpful, Johnny
Patchmaker, Bob User"

...and of course, anything but the first field is optional, so for most
changes, nothing would change as far as the developer is concerned.  The
whole point is to *allow* for better data handling, not to force more
work on every developer.

-- 
Chris Gianelloni
Release Engineering QA Manager/Games Developer
Gentoo Linux

Is your power animal a penguin?