From: L J Bayuk <ljb220@mindspring.com>
To: scrappy@postgresql.org
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Preserving CVS histories / Was: Need new project...
Date: Thu, 19 Feb 2004 21:59:35 -0500 (EST)
Message-ID: <200402200259.i1K2xZCD003326@mindspring.com> (raw)
In-Reply-To: <20040217230736.Q793@ganymede.hub.org>
Marc G. Fournier wrote:
> ...
> -core would be confusing at best ... if you can create the project, I can
> copy the current CVS files (with history) from -core to gborg ... I really
> don't want to lose the changes/history over the past year ...
The project was created Wednesday on Gborg, "pgtclng", but it is still empty.
The actual code changes won't be lost - I have everything from 7.4.1 libpgtcl
in my version now. After a beta release, I will look at your CVS to pick up
post-7.4.1 changes (if any). But I wasn't thinking about file histories,
and they were't going to be copied, I guess. (Gborg pgtcl didn't preserve
histories either. Have other unbundled projects preserved histories?) How
important is this? Is the issue change logs, file deltas, or both?
I'm not a CVS expert, but I understand one needs direct filesystem access
to both CVS repositories to import files with histories. Obviously I can't
do that. Can you? Do you need to be added to the project for this?
I haven't settled on the tree structure. The -core version puts the source
files at the top, Gborg pgtcl used "generic/" (a Tcl / TEA convention), and
I might use a "src/" directory. It's a minor thing, but because of the pain
in moving CVS files around, I need to decide before we put files in. So
first: do you need the histories transfered? If so, I won't add any files,
and I'll tell your where to copy the RCS files into the new project
repository. Then I'll check them out and update them with my versions.
Keep in mind that we still lose the change histories from the Gborg pgtcl
project, I guess. (Not the accumulated changes, just the histories.)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: ljb220@mindspring.com, scrappy@postgresql.org
Subject: Re: Preserving CVS histories / Was: Need new project...
In-Reply-To: <200402200259.i1K2xZCD003326@mindspring.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox