From: "John Netto" <jnetto@sitebrand.com>
To: <help-gnats@gnu.org>
Subject: GNATS utility to move PR between identical databases ?
Date: Wed, 07 May 2003 15:54:00 -0000 [thread overview]
Message-ID: <005201c314af$cb27a070$6e01a8c0@Magoo> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1075 bytes --]
Hi,
RE: Gnats v4.0 beta
Assumption: Two databases where configurations are identical (the files in
gnats-adm are the same except for index and current obviously; only the PRs
themselves are different).
Does anyone have or know where I can get a script to move a PR(s) from one
database to another ?
The application consists of the use of a "feature" database and a
"development" database. The "discussion" database is used to enter "feature"
PRs and filter them. Once they have been edited, validated, discussed, and
parsed, and/or split into multiple feature PRs, these would then be 'moved'
into the "development" database. The "development" database is actually the
primary db which also handles "bug" PRs.
The manual method is to move the PR files from one database to another in
addition to editing the PR# field and renaming the file appropriately.
However, this could be lengthy and is essentially error prone being a manual
process....
Any help would be appreciated..... or perhpas I need to write the script
myself ?
Cheers,
John
[-- Attachment #1.2: Type: text/html, Size: 1571 bytes --]
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next reply other threads:[~2003-05-07 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 15:54 John Netto [this message]
2003-05-07 17:26 McFarland, Ken
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='005201c314af$cb27a070$6e01a8c0@Magoo' \
--to=jnetto@sitebrand.com \
--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).