From: Hugo Gayosso <qztf7k@linux133.powertrain.mpg.gm.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: Yngve Svendsen <yngve.svendsen@clustra.com>,
<gnats-devel@sources.redhat.com>
Subject: Re: New Gnatsweb CVS repository
Date: Thu, 05 Jul 2001 06:02:00 -0000 [thread overview]
Message-ID: <qrgd77fpm8y.fsf@powertrain.mpg.gm.com> (raw)
In-Reply-To: <Pine.BSF.4.33.0107031806190.37042-100000@taygeta.dbai.tuwien.ac.at>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:
> On Mon, 2 Jul 2001, Yngve Svendsen wrote:
> > Gnatsweb 2.6 was imported as the initial version, then a branch named
> > "gnatsweb-v2-branch" was created, and versions 2.7beta, 2.8.0, 2.8.1 and
> > 2.8.2 were committed and tagged in sequence on this branch. In order to
> > check out the tip of the version 2 branch, use the following commands:
>
> Would it have been possible, somehow (with cooperation from the gnu.org
> admins) to instead simply import the original CVS tree, i.e., the CVS
> database files containing the *whole* history?
No problem at all.
Send an email to savannah-hackers@gnu.org telling them this, then send
a tarball of your current CVS tree, and it will be installed.
Greetings,
- --
Hugo Gayosso
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7RGQdx2JZtTN6co8RArToAJ41EdsrmgfCQM7zYpBAoZz5evBniQCgxnlt
V0BEskg69iOsmRMWapi88vo=
=MMuz
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2001-07-05 6:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-01 15:23 Yngve Svendsen
2001-07-02 1:52 ` Gnatsweb / passwords nick
2001-07-02 2:07 ` Yngve Svendsen
2001-07-03 9:08 ` New Gnatsweb CVS repository Gerald Pfeifer
2001-07-03 11:04 ` Yngve Svendsen
2001-07-05 18:13 ` send-pr.el Margaret BRIERTON
2001-07-06 6:55 ` send-pr.el Milan Zamazal
2001-07-05 6:02 ` Hugo Gayosso [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=qrgd77fpm8y.fsf@powertrain.mpg.gm.com \
--to=qztf7k@linux133.powertrain.mpg.gm.com \
--cc=gnats-devel@sources.redhat.com \
--cc=pfeifer@dbai.tuwien.ac.at \
--cc=yngve.svendsen@clustra.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).