This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0218253631==
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigA2FA1F9F3DC53E179475BB88"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigA2FA1F9F3DC53E179475BB88
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

This question came up on a private list, but since it's relevant to many
here I figure I'll post here too.

>> * is there a way to do a server-side clone?
>> The point that if I want to have online a personal clone of KOffice I
don't want
>> to upload a 350Mb repo.

Yep.

There was an admin-defined-command called fork that I had forgotten
about that does just this. Last night, after posing some questions to
Sitaram about it in an IRC message, I woke up this morning to find that
not only does this capability already exist, but that due to my
questions he now has it implemented using the -l flag to git clone so
that it uses hard links when possible, which should help keep space use
down. (This guy rocks!)

Owners of a repository (the creator) can also send a "rmrepo" command to
delete their own clones.

This is also separate from the "personal branches" feature that lets you
have branches for personal work in the main repository but in a specific
namespace (including username).

There are pros and cons to each; in general I prefer the personal
branches approach, although it can mean some more data transfer due to
extra refs/objects, because it a) is far more discoverable and b) these
branches would show up in cgit/redmine, as opposed to personal clones
that would have to either be set up as a subproject in redmine or added
to the cgit configuration (though for the cgit side of things, this
configuration could be created in a scripted fashion). However, these
would have to be used wisely and deleted when possible to avoid an
ever-increasing and unwieldy repository.

--Jeff


--------------enigA2FA1F9F3DC53E179475BB88
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwTpW4ACgkQANYdqNCuGCXusgCfaAOyfJjYjt+vgxrBYFVOBW95
vosAniZ7PGIGVPsI8dEcHLbAm6mpZQJM
=tR27
-----END PGP SIGNATURE-----

--------------enigA2FA1F9F3DC53E179475BB88--

--===============0218253631==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest

--===============0218253631==--