From: Rodrigo Rosenfeld Rosas Date: 2011-01-06T21:14:01+09:00 Subject: [ruby-core:34181] Re: Moving to Git? This is a multi-part message in MIME format. --------------030202010303050200060401 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Em 06-01-2011 10:09, Giuseppe Bilotta escreveu: > On Thu, Jan 6, 2011 at 12:26 PM, Rodrigo Rosenfeld Rosas > wrote: >> Humm, that remembers me that even if you don't mind to have the strange >> checksum as a commit identification, it wouldn't be that easy to change from >> subversion to git regarding the Redmine site. The problem is that since the >> revision names will change, all the existent commit messages refering to svn >> commit identifications will mean nothing after moving to git and so Redmine >> won't be able to associate the commits with the issues, losing the history. > This can actually be solved in a number of possible ways without big > alterations to redmine, such as by tagging each svn-imported commit > with its svn commit id. > > This can be done within the standard tag namespace, possibly with a > common prefix such as svnid/, or within a distinct refs > namespace. Redmine of course would still need to be adapted to turn > the svn commit id links into links to these tags, which is rather > straightforward. Yes, I didn't say it was difficult, just that it was not that easy/straightforward as I was guessing at first. :) Rodrigo --------------030202010303050200060401 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Em 06-01-2011 10:09, Giuseppe Bilotta escreveu:
On Thu, Jan 6, 2011 at 12:26 PM, Rodrigo Rosenfeld Rosas
<rr.rosas@gmail.com> wrote:
Humm, that remembers me that even if you don't mind to have the strange
checksum as a commit identification, it wouldn't be that easy to change from
subversion to git regarding the Redmine site. The problem is that since the
revision names will change, all the existent commit messages refering to svn
commit identifications will mean nothing after moving to git and so Redmine
won't be able to associate the commits with the issues, losing the history.
This can actually be solved in a number of possible ways without big
alterations to redmine, such as by tagging each svn-imported commit
with its svn commit id.

This can be done within the standard tag namespace, possibly with a
common prefix such as svnid/<someid>, or within a distinct refs
namespace. Redmine of course would still need to be adapted to turn
the svn commit id links into links to these tags, which is rather
straightforward.

Yes, I didn't say it was difficult, just that it was not that easy/straightforward as I was guessing at first. :)

Rodrigo
--------------030202010303050200060401--