[Kde-pim] Git migration status

[Torgny Nyblom]

On Sunday 18 April 2010 00.47.41 Thomas McGuire wrote:
[...]
> 1.13 GiB is big, it means I nearly need 100 minutes to clone that. For me
> personally, that would be borderline ok, but this might not be very newbie
> friendly. What do other developers think about this size?

Border line, first clone will be very very slow for most people. After that it 
shouldn't be any problems.

> If it turns out the repo is considered too big, we should reduce it. The
> following comes to my mind, and it should then be measured how much size
> these methods save.
> - Splitting off the e35 and e4 branches into their own repo

This will loose history as history is lost on moves/copies between branches 
not in the same repo.

> - Looking if there are/were single big files that cause a big increase in
> size

None that I could find.

> - Cutting off the history at some defined date

My preferred choice.

[...]
> > History is currently broken when subdirs/files are moved/copied/merged
> > from playground/kdereview, should rules be added for this too? If so any
> > volunteers to help track down what dirs and when?
> 
> I personally think it would be nice to have the history, but not as
> important as other parts of the history.
> As for tracking down the directories and revisions: Does looking at the
> revisions that the script produces as warnings not work? I thought those
> would be the revisions were the history was cut off, and therefore
> punching in those revisions to WebSVN should give you the diff that
> includes from which directory the stuff was moved/copied.

Yes, that is the way, it's just that there are too many of them :)

> > Help needed to check what branches are not in the rulefiles since it's
> > here history is lost.
> 
> What do you mean, are you talking about former SVN branches now being Git
> branches, or about the need to write more rules for moves between branches?
> For the former, I would need to check that by cloning the repo, have you
> uploaded a new copy already?

Yes, it's the former. If you look at the url (for the logs) I gave you you can 
look at the timestamps.

Sorry for not giving this url to the public but I don't think my uplink can 
stand the possible load.


/Regards
Torgny
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/