From: Dirk Bergstrom <dirk@juniper.net>
To: Lars Henriksen <Lars.Henriksen@netman.dk>
Cc: Mel Hatzis <hatzis@juniper.net>, help-gnats@gnu.org
Subject: Re: use of GNATSDB
Date: Fri, 17 May 2002 11:21:00 -0000 [thread overview]
Message-ID: <3CE549A4.7070907@juniper.net> (raw)
In-Reply-To: <20020517181303.GA1558598@cluster2.netman.dk>
On 5/17/2002 11:13 AM, this issued forth from the mind of Lars Henriksen:
> On Fri, May 17, 2002 at 10:31:10AM -0700, Dirk Bergstrom wrote:
>> On 5/17/2002 5:03 AM, this issued forth from the mind of Lars Henriksen:
>> > I can't reproduce this behaviour. Whether GNATSDB is set or not, the command
>> > "pr-edit --lockdb" seems to lock nothing at all. Neither does "pr-edit
>> > --database=<db> --lockdb". On the other hand, "pr-edit --lock <user> <PR>"
>> > honors GNATSDB as well as the --database option.
>> this is a totally different issue.
> Is it? The issue is how or whether GNATSDB is honered by (for example) pr-edit
> and it was claimed, without reservations, that it always ended up locking
> the default database. As far as I can see, you confirm below that this is
> not the case.
i guess i wasn't very clear in my explanation:
using pr-edit in localhost mode, it is IMPOSSIBLE to lock ANY database.
the program locks the db, then unlocks it a few lines later. it's a bug
in the localhost mode code, one of many.
--
Dirk Bergstrom dirk@juniper.net
Computer Geek v: 707.433.0564
Juniper Networks Inc. f: 707.433.0769
"it *looks* like a nail; lemme grab my hammer..."
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
prev parent reply other threads:[~2002-05-17 18:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 19:24 Mel Hatzis
[not found] ` <15525.34645.542865.70528@habakuk.home.ha-schneider.de>
[not found] ` <3CA6046B.1060004@juniper.net>
[not found] ` <15528.10405.211358.551224@habakuk.home.ha-schneider.de>
2002-04-30 22:18 ` Mel Hatzis
2002-05-17 5:06 ` Lars Henriksen
2002-05-17 5:24 ` Lars Henriksen
2002-05-17 5:30 ` Lars Henriksen
2002-05-17 11:09 ` Mel Hatzis
2002-05-17 11:33 ` Lars Henriksen
2002-05-17 10:33 ` Dirk Bergstrom
2002-05-17 11:15 ` Lars Henriksen
2002-05-17 11:21 ` Dirk Bergstrom [this message]
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=3CE549A4.7070907@juniper.net \
--to=dirk@juniper.net \
--cc=Lars.Henriksen@netman.dk \
--cc=hatzis@juniper.net \
--cc=help-gnats@gnu.org \
/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).