Dear diary, on Tue, Oct 17, 2006 at 04:41:02PM CEST, I got a letter where Jakub Narebski <jnareb@xxxxxxxxx> said that... > "Bundle" equivalent, although binary in nature, would be thin pack. It should be noted that there's no user interface for sending/receiving that and I suspect no reasonably usable user interface for creating it. How frequently are the bundles used in practice? It's a cultural difference, I suspect. Git comes from an environment based on intensive exchanges of patches and patch series and an environment not mandating developers to use any tool besides diff/patch, so Git is very focused at good support for applying patches and there simply has been no big conscious demand for bundles support given this. Another aspect of this is that Git (Linus ;) is very focused on getting the history right, nice and clean (though it does not _mandate_ it and you can just wildly do one commit after another; it just provides tools to easily do it). This means that the downstream maintainers have to rebase patches, possibly reorder them, and update the changesets with bugfixes instead of stacking the bugfixes upon them in separate changes - then Linus merges the patches and only at that point they are "etched" forever. This means that the history will contain neatly laid out way of how $FEATURE was achieved, but of course also more work for downstream maintainers. -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ #!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj $/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1 lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/) - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html