Re: Current state of my ideas on moving docs to GIT
| From: | Oliver Albers | Date: | Sat, 02 Mar 2019 11:51:18 +0000 |
| Subject: | Re: Current state of my ideas on moving docs to GIT | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969387183@lists.php.net to get a copy of this message | ||
Hello again everyone,
> Here is the first step that I think needs to happen: Perform a svn2git conversion of the doc-en
> repo, push it to git@git.php.net:/doc/en.git and setup a cron job to keep it up to date with new
> changes coming in from SVN.
>
> There is a little more, here. Every SVN commit number must be mapped to respective git hash,
> for past and future commits. So every translation tag, who points to SVN numbers, can be latter
> converted. These SVN number are old and new. Some of then, very, very old.
>
> Yes, of course. That is why I suggested to start with a conversion of doc-en first, because no
> revision remapping is necessary there. Translation repositories are the next step, which will first
> require a filter-branch rewrite of history and then on-the-fly rewrites whenever we sync new svn
> commits.
So, I had looked into it again this week and saw that the first step is already done, at least the
repository at http://git.php.net/?p=doc/en.git;a=summary
<http://git.php.net/?p=doc/en.git;a=summary>
seems fairly up to date. And the conversion does contain the necessary metadata to extract the
mapping between SVN revisions and git hashes (git-svn-id).
So wat would be the next step? I guess we would try to automatically update all the translations and
add a tag similar to „EN-Revision“ which contains the commit hash, e.g. a new „EN-Commit“
tag, so that in the next step recheck can be updated to use this new information?
Regards,
Oliver