From: Rodrigo Rosenfeld Rosas <rr.rosas@...>
Date: 2011-01-07T19:59:17+09:00
Subject: [ruby-core:34216] Re: Moving to Git?

This is a multi-part message in MIME format.
--------------070206070902000306030904
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

  Em 07-01-2011 03:59, "Martin J. D�rst" escreveu:
> On 2011/01/06 20:26, 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.
>>
>> So, we would need to make some program for collecting this pattern from
>> the commit messages and substitute them by the appropriate checksum
>> rewriting the messages. This would certainly break the official github
>> mirror, but that is a minor problem.
>
> Changing mails is a bad idea, because it's changing what people have 
> said. I think it needs to be done the other way round: When converting 
> to git, with each git commit, store the original svn revision number 
> somewhere (e.g. in the comment, with some special tagging). Then, make 
> Redmine find the commits using this special tagging.
>
> Regards,   Martin.
>
Yes, I agreee. I was thinking in an alternative for avoiding the need to 
change Redmine for easing keeping up-to-date with Redmine trunk, but 
that is ok to change Redmine a bit more...

Regards, Rodrigo.

--------------070206070902000306030904
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Em 07-01-2011 03:59, "Martin J. D&uuml;rst" escreveu:
    <blockquote cite="mid:4D26ABCA.9070503@it.aoyama.ac.jp" type="cite">On
      2011/01/06 20:26, Rodrigo Rosenfeld Rosas wrote:
      <br>
      <br>
      <blockquote type="cite">Humm, that remembers me that even if you
        don't mind to have the strange
        <br>
        checksum as a commit identification, it wouldn't be that easy to
        change
        <br>
        from subversion to git regarding the Redmine site. The problem
        is that
        <br>
        since the revision names will change, all the existent commit
        messages
        <br>
        refering to svn commit identifications will mean nothing after
        moving to
        <br>
        git and so Redmine won't be able to associate the commits with
        the
        <br>
        issues, losing the history.
        <br>
        <br>
        So, we would need to make some program for collecting this
        pattern from
        <br>
        the commit messages and substitute them by the appropriate
        checksum
        <br>
        rewriting the messages. This would certainly break the official
        github
        <br>
        mirror, but that is a minor problem.
        <br>
      </blockquote>
      <br>
      Changing mails is a bad idea, because it's changing what people
      have said. I think it needs to be done the other way round: When
      converting to git, with each git commit, store the original svn
      revision number somewhere (e.g. in the comment, with some special
      tagging). Then, make Redmine find the commits using this special
      tagging.
      <br>
      <br>
      Regards,&nbsp;&nbsp; Martin.
      <br>
      <br>
    </blockquote>
    <font face="DejaVu Sans">Yes, I agreee. I was thinking in an
      alternative for avoiding the need to change Redmine for easing
      keeping up-to-date with Redmine trunk, but that is ok to change
      Redmine a bit more...</font><br>
    <br>
    Regards, Rodrigo.<br>
  </body>
</html>

--------------070206070902000306030904--