#3: Migrate Olena 0.11 (and previous revisions) from PRCS to Git --------------------------+------------------------------------------------- Reporter: levill_r | Owner: levill_r Type: enhancement | Status: reopened Priority: blocker | Milestone: Olena 0.11.1 Component: other | Version: 0.11 Resolution: | Keywords: prcs subversion svn git --------------------------+------------------------------------------------- Changes (by levill_r): * keywords: prcs subversion svn => prcs subversion svn git * status: closed => reopened * resolution: wontfix => Old description:

'''No further development should be done on the 0.11 branch until this task is either fixed or removed.'''

This task is an open discussion. I haven't much tried to convert the PRCS Olena repository to a Subversion one, and I think it '''is''' really feasible, though not trivial. If you're interested in this migration, please ask me (Roland) first before making actual changes to the PRCS or the SVN repository.

New description: Use `prcs2git` (http://takaki-web.media-as.org/my_works/prcs2git) to convert the old PRCS revisions of Olena to Git. I (Roland) made an attempt and successfully converted the whole repository (minus two bogus revisions, namely 10.138 and 10.139) by using it. However there is room for improvement: * ignoring revisions is not possible (there should be an option taking an ignore pattern as argument) * information about author and committer (name, e-mail, date) is not propagated; * log title (short messages) are filled with PRCS metadata (ugly!) ; we should retrieve the title from somewhere (PRCS, the !ChangeLog(s) or even the mailing list); * log messages are meaningless. Branches, however, have been well translated. '''Remember that no further development should be done on the 0.11 branch until this task is either fixed or removed.''' -- Comment: s/Subversion/Git/. -- Ticket URL: <https://trac.lrde.org/olena/ticket/3#comment:8> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.