On Monday, 5 de September de 2011 16:39:29 Oswald Buddenhagen wrote: > On Mon, Sep 05, 2011 at 03:37:09PM +0200, Johannes Sixt wrote: > > Am 9/5/2011 15:30, schrieb Ian Monroe: > > > Correct me if I'm wrong, but you can't commit with shallow downloads > > > so they are of course pretty useless for development. You can develop > > > with a SVN checkout, which is always shallow. > > > > Point taken: You can't push from a shallow clone. > > not quite correct, actually ... > http://git.661346.n2.nabble.com/pushing-from-a-shallow-repo-allowed-tt233225 > 2.html#a2421456 i.e., with a straight history it will work just fine.
I've always wondered why pushing from a shallow clone didn't work. It's the
client (the shallow repo) that decides what objects to send and it has all the
objects it needs. Isn't it?
I understand why you can never update it (fetch into it), since the remote may
conclude that it doesn't need to send some objects.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Software Architect - Intel Open Source Technology Center
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
