[Kde-pim] Git migration status
Martin Steigerwald
Martin at lichtvoll.de
Sun Apr 18 12:27:53 BST 2010
Hi Torgny,
Am Sonntag 18 April 2010 schrieb Torgny Nyblom:
> > 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.
Wouldn't it be possible to have the complete history in the repo, but only
check out the last revisions? Then there could be some user instructions
on how to do that.
I am pretty much sure Bazaar can do that, and I think git should be able
to do that as well. Hmmm, from the manpage of git-clone:
--depth <depth>
Create a shallow clone with a history truncated to the
specified number of revisions. A shallow repository
has a number of limitations (you cannot clone or fetch
from it, nor push from nor into it), but is adequate
if you are only interested in the recent history of a
large project with a long history, and would want to
send in fixes as patches.
Quite restricted, but at least suitable to send patches. Actually it does
not make sense to me why pushing does not work with those shallow
repository.
If history is cut off, I find it would be nice if there could a second repo
with full history for archival purposes.
Anyway just suggestions, my last and only contribution (CRM114 antispam
configuration for KMail) lays years back.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20100418/658d984e/attachment.sig>
-------------- next part --------------
_______________________________________________
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/
More information about the kde-pim
mailing list