<div dir="ltr">Hi Helmut,<div><br></div><div>there was no reaction from you after Ernesto's reply. Do you disagree about the plans? Do have anything to add?</div><div style><br></div><div style>Here is the current state of the migration script which Thomas created:</div>
<div style><a href="https://gist.github.com/tmaroschik/6f1b36a71dbe0ab0e1f8">https://gist.github.com/tmaroschik/6f1b36a71dbe0ab0e1f8</a><br></div><div style><br></div><div style>And this is the result of it: <a href="https://github.com/tmaroschik/TYPO3-Core-Without-Submodules">https://github.com/tmaroschik/TYPO3-Core-Without-Submodules</a></div>
<div style><br></div><div style>What we plan to do is this:</div><div style><br></div><div style>1. Announce a merge freeze</div><div style>2. Run the script again on the current repository (this will take 1.5-2 hours)</div>
<div style>3. Push the changes</div><div style><div><br></div><div>Additionally, we will rename the repository to <a href="http://git.typo3.org/Packages/TYPO3.CMS.git">git.typo3.org/Packages/TYPO3.CMS.git</a></div><div><br>
</div><div style>Greetings, Michael<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2013/5/18 Helmut Hummel <span dir="ltr"><<a href="mailto:helmut.hummel@typo3.org" target="_blank">helmut.hummel@typo3.org</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<div class="im"><br>
<br>
On 15.05.13 10:57, Michael Stucki wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We see a lot of problems coming if Git history will be rewritten.<br>
</blockquote>
<br></div>
Can you elaborate on the problems?<br>
I would still prefer the history rewrite.<br>
<br>
My suggestion would be to:<br>
<br>
1. Create a new repo and Gerrit project following the new naming scheme<br>
2. Fill the new repo with the rewritten history<br>
3. Make the old repo read only<br>
optional: Have a script to transfer all open changes in Gerrit to the new Project.<br>
<br>
Benefits:<br>
<br>
* Clean history<br>
# No hassels when fetching older versions where submodules are used<br>
# Working git blam without manual interaction<br>
* No breaking changes for clones of the "old" repo<br>
<br>
Downsides:<br>
* Merge freeze for the time until the new repo is ready (1 Day?)<br>
* Bit of more work for tranfering open change requests<br>
* forge core project could have broken associated merges in the tickets<br>
<br>
Are there more downsides? Or dou you consider the last one as blocker (which I would understand)?<br>
<br>
<br>
Kind regards,<br>
Helmut<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Helmut Hummel<br>
Release Manager TYPO3 6.0<br>
TYPO3 Core Developer, TYPO3 Security Team Member</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
TYPO3 .... inspiring people to share!<br>
Get involved: <a href="http://typo3.org" target="_blank">typo3.org</a><br>
______________________________<u></u>_________________<br>
Before posting to this list, please have a look to the posting rules<br>
on the following websites:<br>
<br>
<a href="http://typo3.org/teams/core/core-mailinglist-rules/" target="_blank">http://typo3.org/teams/core/<u></u>core-mailinglist-rules/</a><br>
<a href="http://typo3.org/development/bug-fixing/diff-and-patch/" target="_blank">http://typo3.org/development/<u></u>bug-fixing/diff-and-patch/</a><br>
______________________________<u></u>_________________<br>
TYPO3-team-core mailing list<br>
<a href="mailto:TYPO3-team-core@lists.typo3.org" target="_blank">TYPO3-team-core@lists.typo3.<u></u>org</a><br>
<a href="http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core" target="_blank">http://lists.typo3.org/cgi-<u></u>bin/mailman/listinfo/typo3-<u></u>team-core</a><br>
</div></div></blockquote></div><br></div></div>