> Nicola wrote;
>
>> Stefano Mazzocchi wrote:
>> ...
>> > Ok, what about moving all the code to subversion and just keep
>> > the metadata in CVS? (at least for now)
>>
>> IIRC that what we had basically agreed was a sensible thing to do
>> for Python Gump.
>>
>> +1 from me
+1 from me as well.
On Thu, 15 Jul 2004, Adam R. B. Jack <[EMAIL PROTECTED]> wrote:
> Yeah, I think we agree that is the best mid-term solution, I was
> just (1) nervous about making an SVN request ('cos of delays in
> getting the resources configured/converted)
No problem.
> (2) hoping to clean out/re-organize now (prior to any such 1 above).
As long as we keep the history of "traditional" in CVS I don't care
too much whether it gets migrated to SVN at all. It's not as if we'd
remove the CVS module completely, it will just become unused.
> Big questions (1) folks ok w/ me doing a clean/re-org prior to
> importing into SVN?
See above.
> (2) do we want to preserver history?
Yes.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
