From: Mel Hatzis <hatzis@juniper.net>
To: Mike Hoolehan <mike@sycamore.us>
Cc: ishafqat@xavor.com, help-gnats@gnu.org
Subject: Re: New PR ID needed after inserting through GNATSD ..
Date: Tue, 24 Feb 2004 20:28:00 -0000 [thread overview]
Message-ID: <403BA130.9090607@juniper.net> (raw)
In-Reply-To: <1077640797.4138.4.camel@localhost.localdomain>
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 <hatzis@juniper.net>, Andrew J. Gray
<andrewg@gnu.org>
* 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
>>Help-gnats@gnu.org
>>http://mail.gnu.org/mailman/listinfo/help-gnat
>
> s
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Help-gnats mailing list
> Help-gnats@gnu.org
> http://mail.gnu.org/mailman/listinfo/help-gnats
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2004-02-24 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 11:21 Imran Shafqat
2004-02-24 16:52 ` Mike Hoolehan
2004-02-24 20:28 ` Mel Hatzis [this message]
2004-02-25 7:05 Imran Shafqat
2004-02-25 8:13 ` Mel Hatzis
2004-02-25 14:17 ` Tim Buck
2004-02-25 14:52 ` Yngve Svendsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=403BA130.9090607@juniper.net \
--to=hatzis@juniper.net \
--cc=help-gnats@gnu.org \
--cc=ishafqat@xavor.com \
--cc=mike@sycamore.us \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).