Re: Tcl.pm repo
[email protected] (Gisle Aas)
| Newsgroups | perl.tcltk |
|---|---|
| Message-ID | <[email protected]> |
On Sep 1, 2009, at 22:20 , Gisle Aas wrote:
> On Sep 1, 2009, at 21:11 , Konovalov, Vadim (Vadim)** CTR ** wrote:
>
>>> First attempt at converting the CVS repo from sourceforge has
>>> now been
>>> performed. You can investigate and grab the result from:
>>>
>>> http://github.com/gisle/tcl.pm/commits/master
>>>
>>> The tagging in the CVS repo appear to be lacking (the only tags that
>>> appeared was Tcl-0-{72,75,85}) so I will spend a little time trying
>>> verify the converted result and try to recreate some tags
>>> matching the
>>> most recent CPAN releases at least.
>>>
>>> It seems like the history of the CVS repo starts with "Author: Jeff
>>> Hobbs <[email protected]>; Date: Mar 22 2004; initial import of
>>> Vadim's Tcl-0.72 Perl/Tcl bridge module into sf cvs". If you happen
>>> to have a repo of earlier history, then we could add that to the GIT
>>> repo as well.
>>>
>>
>> very much thanks!
>> Will I be able to commit there? (I've just created my new user
>> "vadrer")
>
> That can be set up or you can 'fork' it and we just define that as
> the canonical version. If you can wait a little bit until the
> conversion from CVS is "perfect" that would be good. Might not be
> until tomorrow.
At this point I'm happy with the state of this repo. It seems to be
in shape suitable for continued development.
The main branch contains captures the work that was done in the
tcltkce repo at sourceforge and there is a 'cpan' branch captures the
earlier history. It would be preferable to join these histories and I
might look into that at some point (nice to have 'git blame' to be
able to pinpoint where all code comes from), but since I don't
actually know how to get to there right now that needs more research.
You have now been given access to push to "my" github repo; but since
this is really your project feel free to 'fork' the project to your
github namespace and we'll make that the "official" version.
I will go offline for the weekend tomorrow so I don't expect to get to
the patching I really wanted to do until next week. Since this is Git
it might actually be that I'll get this done while offline, but for
all I know there might be better things to do up in the mountains of
Norway :-)
--Gisle