On 9/18/07, Kristis Makris <[EMAIL PROTECTED]> wrote: > On Tue, 2007-09-18 at 08:46 +0200, Gianluca Sforna wrote: > > I'm missing several details here. For a start: who's composing such > > messages? > > Users compose such messages when they commit. This is part of their log > message.
Oh, I see... > > > Anyway, if that string is going to be parsed, it needs either a > > separator different from the space like in: > > > > status 547 : resolved : unable to reproduce > > > > or quoting the string containing spaces like: > > > > status 547 : resolved "unable to reproduce" > > I can see an argument that some bug-trackers may define resolution > states like "resolved:fixed", with the ":" still throwing us off. > Quoting seems more safe, but can be a pain to type. But then so is the > "_". Hmmmm.... > So in above the example the commit is meant to modify the status of bug 547? if so, I see the additional caveat: strictly speaking, resolved is the status, but "unable to reproduce" is another field ( resolution ), so you may also consider spiltting the "command" in more lines like: status 547: resolved resolution 547: unable to reproduce _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
