Posted Nov 18, 2010 12:09 UTC (Thu) by jnareb
Parent article: LPC: Michael Meeks on LibreOffice and code ownership
At this point, Michael decided that we'd had enough and needed a brief technical break. So he talked about Git: the LibreOffice project likes to work with shallow clones because the full history is so huge. But it's not possible to push patches from a shallow clone, that is a pain. Michael also noted that git am is obnoxious to use.
About shallow clones: perhaps now that large project (and large number of contributors) is using them, those issues would be fixed. There was even some work in progress presented on git mailing list adding support for lazy/sparse clones (in addition to recently added support for sparse checkouts), which generalizes also shallow clones, and which has support for narrowing and widening selection; if I remember correctly this would allow to push from narrow clone to narrow clone etc. But this was one person show...
About git am: what were the problems with it? Why the complaint wasn't posted on git mailing list, for git developers to be aware of it?
to post comments)