Re: [Trans-devel] Patches available

[Claude B. <Cla...@li...>]

Hi Giulio,
Sorry for the delay answering you, the start of the academic semester has been a bit busy for me...
Thanks a lot for your exploration on CVS to Git conversion! I just activated a Git repository on the 
Sourceforge Transcriber project in addition to the initial CVS and I hope it will work as expected - 
I don't know if there is a difference between the Sourceforge and Github web interface for Git, 
anyway it doesn't hurt to have several git repository since it is not centralized.
I will probably be able to import directly your project. As far as I remember, the CVS was not left 
in a stable state, and it would be safer to revert back to the distributed 1.5.1 version (but this 
can probably be easily handled at Git level).
Best,
   Claude

Le 13/09/13 15:42, Giulio Paci a écrit :
> Hi Claude,
> 	I was curious about how to migrate a CVS repository to git, so I tried
> to migrate the current transcriber CVS repository.
>
> I used cvs2git to do the first conversion, then I manually replaced user
> names in the files generated by cvs2git, then I imported those files in
> a git repository and finally I cloned the repository.
>
> The two latest steps were to remove CVSROOT, to move transcriber content
> to the main directory of the repository and to rename the tags.
>
> I achieved this with:
>
> # CVSROOT removal
> git filter-branch -f --force --index-filter 'git rm -rf --cached
> --ignore-unmatch CVSROOT' --prune-empty --tag-name-filter cat -- --all
> rm -rf .git/refs/original/; git reflog expire --expire=now --all; git gc
> --prune=now; git gc --aggressive --prune=now
>
> # move transcriber content
> git filter-branch  -f --force --index-filter --tree-filter 'if test -d
> transcriber; then (ls -d transcriber/*; echo .) | xargs mv ;fi'
> --prune-empty --tag-name-filter cat -- --all
> rm -rf .git/refs/original/; git reflog expire --expire=now --all; git gc
> --prune=now; git gc --aggressive --prune=now
>
> and finally manual tag renaming.
>
> The result is in https://github.com/giuliopaci/transcriber
>
> You can browse the history here:
> https://github.com/giuliopaci/transcriber/commits
>
> Maybe you can use this repository to migrate the old CVS repository on
> sourceforge to git.
>
> Bests,
> 	Giulio.
>
> On 11/09/2013 14:40, Giulio Paci wrote:
>> Hi Claude,
>> 	any news?
>>
>> Bests,
>> 	Giulio.
>>
>> On 29/08/2013 17:45, Claude Barras wrote:
>>> Hi, this is a good idea; I have also been using git for recent projects
>>> and I will have a look at the switch.
>>> Best,
>>>    Claude
>>>
>>>
>>> Le 29/08/13 00:01, Giulio Paci a écrit :
>>>> Il 26/08/2013 15:44, Claude Barras ha scritto:
>>>>> Thanks a lot for your contribution! As a matter of fact, updating the
>>>>> legacy Transcriber is long overdue (and binaries for modern versions
>>>>> of Windows and MacOS are
>>>>> missing), because of lacking time and resource. A newer C++ version
>>>>> (TransAG) has been developped in between even if it is currently not
>>>>> very active either.
>>>>> But if you can invest some time on it, you could become developer
>>>>> member on the Sourceforge site and include your updates yourself? Let
>>>>> me know about your use of
>>>>> Transcriber and if you are interested!
>>>> I know about TransAG, but my colleagues (we are working only with
>>>> audio) did not find it a viable alternative to the legacy transcriber
>>>> (we are used to the legacy
>>>> interface, shortcuts, ...).
>>>> Moreover we also have several tools that automatically process .trs
>>>> files that are not exported by TransAG.
>>>>
>>>> We are currently using transcriber to transcribe and annotate audio
>>>> streams (mostly children interaction with a robot).
>>>>
>>>> I have very few time, but I will be more than happy to contribute to
>>>> Transcriber (and eventually TransAG). Do you think it would be
>>>> possible to convert the current
>>>> repository to a git-based repository? I think it is much more
>>>> convenient to use than CVS.
>>>>
>>>> Bests,
>>>>      Giulio.
>>>>
>>>>> Le 06/08/13 17:36, Giulio Paci a écrit :
>>>>>> Dear Transcriber Team,
>>>>>>      during the last year I have written several patches that I would
>>>>>> like to see included in transcriber.
>>>>>> Is it possible? Is it possible that a new bug-fix release of the
>>>>>> legacy transcriber will be released in future?
>>>>>>
>>>>>> Attached are the patches that I think are ready to be included, they
>>>>>> apply (in order) cleanly to the latest release on sourceforge.
>>>>>>
>>>>>> Bests,
>>>>>>      Giulio.
>>>>>>
>>>>>>

-- 
LIMSI-CNRS                    tel: +33 1 69 85 81 84
bat. 508, BP 133              fax: +33 1 69 85 80 88
Univ Paris-Sud
91403 Orsay cedex France      web: http://www.limsi.fr/Individu/barras/