process_bug.cgi as backend and dontchange

Christian Reis kiko at async.com.br
Fri Oct 25 21:06:07 UTC 2002


On Fri, Oct 25, 2002 at 09:46:05PM +0100, Gervase Markham wrote:
> Christian Reis wrote:
> 
> > So, I'm hacking away at this CVS->Bugzilla client.
> >
> > Context: it's a *pure* HTTP client - all it does is connect to
> > process_bug.cgi, and send in a well-formed form that updates a single
> > bug. If I want to add a comment to many bugs, I'll do multiple HTTP
> > requests, no problem.
> >
> > Problem: there is no way to specify dontchange if you are changing a
> > single bug. What I want is to add a single comment - and process_bug
> > wants *all* the fields defined. dontchange would be a nice way to work
> > around that, except for the fact that the tests in process_bug only look
> > at dontchange if it's a multiple bug change.
> 
> Fine. Fake one that happens to only change one bug :-) Define the bug_id 

This hack is better than one that defines a policy for process_bug.cgi
of "if value == value of dontchange" ignore it? It would make things
simpler to understand..

Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 261 2331 | NMFL



More information about the developers mailing list