From: Daniel Quimper <dq@ubit.com>
To: "Mohamed Niyaz, ASDC Chennai" <mohamedn@msdc.hcltech.com>,
help-gnats@gnu.org
Subject: Re: Import bug utility for GNATS?
Date: Tue, 16 Mar 2004 02:57:00 -0000 [thread overview]
Message-ID: <opr4xotkj4p1d9bh@127.0.0.1> (raw)
In-Reply-To: <A125AF3F419E97458A237BE2484C3C8B0DB07140@pluto.msdc.hcltech.com>
Hi,
I got a suggestion for you. Use a software like "unison" to sync your two
installations.
Your user don't have to export and import the PR, that would be done
automatically
with "unison" a couple of minutes after the insertion. Since, Gnats is all
file base, I
think this would work well. Unison is not the only software for this, only
one that I
use for other purpose.
I don't really understand why you would need two servers though. Can you
have only
on location and have the second location access it via VPN or some other
network
facility?
dan...
On Thu, 4 Mar 2004 18:00:12 +0530, Mohamed Niyaz, ASDC Chennai
<mohamedn@msdc.hcltech.com> wrote:
>
> Hello All:
>
> I am considering using two GNATS servers in different locations (in
> separate
> VPNs) and was wondering if we could import bugs from one to another. I
> mean,
> somebody enters a bug in one server and instead of having to repeat the
> same
> thing for the second one, export from the first one and then import to
> the
> second one? Any help would me much appreciated.
>
> Thanks.
--
Daniel Quimper
dq@ubit.com
Mobile: +81-90-4456-3168
Phone: +81-3-5804-0104
Fax: +81-3-5804-0105
Ubiquitous Business Technology, Inc.
http://www.ubit.com
3-42-5 Hongo Bunkyo-ku, Tokyo 113-0033, Japan
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
prev parent reply other threads:[~2004-03-16 2:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 11:03 Mohamed Niyaz, ASDC Chennai
2004-03-16 2:57 ` Daniel Quimper [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=opr4xotkj4p1d9bh@127.0.0.1 \
--to=dq@ubit.com \
--cc=help-gnats@gnu.org \
--cc=mohamedn@msdc.hcltech.com \
/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).