Re: New PR ID needed after inserting through GNATSD ..

Mel Hatzis <[email protected]>
Newsgroups gmane.comp.bug-tracking.gnats.general
Message-ID <[email protected]>
On 02/24/2004 11:01 PM, Imran Shafqat submitted:
> Thanks for your reply.
> Can you tell how can I use this patch through GNATSD ? 

You'll need to get the current development version of GNATS
from CVS...it contains very few changes from GNATS 4.0 and,
IMO, it's just as reliable.

Follow the instructions for "Getting a Copy of the CVS Repository"
on http://savannah.gnu.org/cvs/?group=gnats if you want to
know how this is done.

will SUBM command
> return new PR number ?

Assuming the SUBM command succeeds and creates, say, PR 1969,
it would return the following:

351-The added PR number is:
350 1969

As for the GNATS client utilities...

   - pr-edit will return the new PR number if it is
     invoked with a (new) --show-prnum option which
     is relevant if the --submit option is also
     present

   - send-pr will always return something like:

       send-pr: problem report 1969 filed

     (it now invokes pr-edit with the '--show-prnum' option)

--
Mel Hatzis

> 
> Thanks in advance
> Regards
> 
> Imran Shafqat
> Software Engineer
> Xavor Pakistan.
> 
> 
> -----Original Message-----
> From: Mel Hatzis [mailto:[email protected]] 
> Sent: Wednesday, February 25, 2004 12:09 AM
> To: Mike Hoolehan
> Cc: [email protected]; Imran Shafqat
> Subject: Re: New PR ID needed after inserting through GNATSD ..
> 
> Actually, the latest version of the GNATS sources has a patch for
> returning the new PR number. This is one of the few changes
> made after GNATS 4.0 was released. Here's the ChangeLog entry:
> 
> 2003-08-30  Mel Hatzis  <[email protected]>, Andrew J. Gray
> <[email protected]>
> 
>          * client.c (get_reply): Check for outfp being NULL.
>          (netSendPRCmd): Add flag to show information received.  All
>          callers changed.
>          * cmds.c (GNATS_subm): Send PR number for new submission.
>          * file-pr.c (submit_pr): Return PR number for new submission.
>          * pr-edit.c (long_options, handleNetworkEdit, main): Add
>          show_prnum option.
> 
> If you opt to try this, be aware that it's a change to the GNATS
> client/server interface (if you're using GNATS in network mode),
> so you'll need to update the GNATS client binaries in addition
> to the server.
> 
> -Mel
> 
> On 02/24/2004 08:39 AM, Mike Hoolehan submitted:
> 
>>I maintain a perl module for communication with the gnats daemon.  I
>>originally intended to do the same thing as you for my "submitPR"
> 
> method
> 
>>(i.e. return the PR Number of the newly created PR) but instead
> 
> decided
> 
>>only to return true/false (depending on success/failure).  As far as I
>>know, since gnatsd doesn't supply the information on PR creation, the
>>only way to reliably get the PR number of a new PR is to query again
> 
> for
> 
>>the exact same criteria.
>>
>>I left it up to my user to find the PR number of his/her new PR.
>>
>>Mike
>>
>>
>>On Tue, 2004-02-24 at 13:16, Imran Shafqat wrote:
>>
>>
>>>Dear All,
>>>
>>>I am writing GNATSD client in C#.Net. I need to push back the new PRID
>>>generated by GNATS to the client. I have multiple clients that can
>>>simultaneously enter new PRS. Can any one please guide me what is the
>>>best way to return / get the PRID from the GNATS after insertion.
>>>
>>>
>>>
>>>Thanks in advance.
>>>
>>>
>>>
>>>Regards
>>>
>>>Imran Shafqat
>>>
>>>Software Engineer
>>>
>>>Xavor Pakistan
>>>
>>>
>>>
>>>______________________________________________________________________
>>>_______________________________________________
>>>Help-gnats mailing list
>>>[email protected]
>>>http://mail.gnu.org/mailman/listinfo/help-gnat
>>
>>s
>>
>>
>>
> 
> ------------------------------------------------------------------------
> 
>>_______________________________________________
>>Help-gnats mailing list
>>[email protected]
>>http://mail.gnu.org/mailman/listinfo/help-gnats
> 
> 
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.