Comments for internal fragmentation http://www.selenic.com/blog a personal journal of hacking, science, and technology Mon, 09 May 2011 11:40:35 +0000 hourly 1 http://wordpress.org/?v=3.2.1 Comment on Mercurial 1.9 sprint, day one by Seb http://www.selenic.com/blog/?p=712&cpage=1#comment-38 Seb Mon, 09 May 2011 11:40:35 +0000 http://www.selenic.com/blog/?p=712#comment-38 Ok, I am going to contact him. Ok, I am going to contact him.

]]> Comment on Mercurial 1.9 sprint, day one by Martin Geisler http://www.selenic.com/blog/?p=712&cpage=1#comment-37 Martin Geisler Mon, 02 May 2011 07:25:27 +0000 http://www.selenic.com/blog/?p=712#comment-37 Seb: please contact the author of RebaseIf and ask him to push it to us on the Mercurial mailinglist. Instead of making a new extension, it should be very easy to integrate the logic into the existing rebase extension. Seb: please contact the author of RebaseIf and ask him to push it to us on the Mercurial mailinglist. Instead of making a new extension, it should be very easy to integrate the logic into the existing rebase extension.

]]> Comment on Mercurial 1.9 sprint, day one by Seb http://www.selenic.com/blog/?p=712&cpage=1#comment-36 Seb Sat, 30 Apr 2011 09:43:33 +0000 http://www.selenic.com/blog/?p=712#comment-36 I REALLY hope rebaseif (http://mercurial.selenic.com/wiki/RebaseIfExtension) extension functionnality could be bundled with Mercurial 1.9 and rebase + rebaseif activated by default. Rebaseif extension make using Mercurial so easy, really, it is a must have for all users !!! I REALLY hope rebaseif (http://mercurial.selenic.com/wiki/RebaseIfExtension) extension functionnality could be bundled with Mercurial 1.9 and rebase + rebaseif activated by default.

Rebaseif extension make using Mercurial so easy, really, it is a must have for all users !!!

]]> Comment on How to structure a software project to have a minimum risk of corporate takeover by Tweets that mention How to structure a software project to have a minimum risk of corporate takeover « internal fragmentation -- Topsy.com http://www.selenic.com/blog/?p=699&cpage=1#comment-31 Tweets that mention How to structure a software project to have a minimum risk of corporate takeover « internal fragmentation -- Topsy.com Tue, 21 Dec 2010 21:31:50 +0000 http://www.selenic.com/blog/?p=699#comment-31 [...] This post was mentioned on Twitter by Jim Pick and others. Jim Pick said: RT @mpmselenic: How to structure a software project to have a minimum risk of corporate takeover: http://www.selenic.com/blog/?p=699 #me ... [...] [...] This post was mentioned on Twitter by Jim Pick and others. Jim Pick said: RT @mpmselenic: How to structure a software project to have a minimum risk of corporate takeover: http://www.selenic.com/blog/?p=699 #me … [...]

]]> Comment on The 1.7 Mercurial Sprint by Iteration 1045 – Mercurial 1.7 – Bitbucket http://www.selenic.com/blog/?p=681&cpage=1#comment-28 Iteration 1045 – Mercurial 1.7 – Bitbucket Wed, 17 Nov 2010 21:39:42 +0000 http://www.selenic.com/blog/?p=681#comment-28 [...] seems just like yesterday that we were in Chicago for the sprint to get Mercurial 1.7 out the door, which happened on Nov [...] [...] seems just like yesterday that we were in Chicago for the sprint to get Mercurial 1.7 out the door, which happened on Nov [...]

]]> Comment on The 1.7 Mercurial Sprint by Tweets that mention The 1.7 Mercurial Sprint « internal fragmentation -- Topsy.com http://www.selenic.com/blog/?p=681&cpage=1#comment-26 Tweets that mention The 1.7 Mercurial Sprint « internal fragmentation -- Topsy.com Thu, 04 Nov 2010 23:33:01 +0000 http://www.selenic.com/blog/?p=681#comment-26 [...] This post was mentioned on Twitter by Burak Gürsoy, bboissin, Steve Losh, Augie Fackler, Matt Mackall and others. Matt Mackall said: Finally did a write-up of the #Mercurial 1.7 sprint (with group photo): http://www.selenic.com/blog/?p=681 [...] [...] This post was mentioned on Twitter by Burak Gürsoy, bboissin, Steve Losh, Augie Fackler, Matt Mackall and others. Matt Mackall said: Finally did a write-up of the #Mercurial 1.7 sprint (with group photo): http://www.selenic.com/blog/?p=681 [...]

]]> Comment on Mercurial: adding ‘unified’ tests by Adrian Buehlmann http://www.selenic.com/blog/?p=663&cpage=1#comment-25 Adrian Buehlmann Tue, 28 Sep 2010 07:22:27 +0000 http://www.selenic.com/blog/?p=663#comment-25 See also http://pypi.python.org/pypi/cram (which has a nice short description of it's syntax -- which is mostly the same as mercurial's unified tests). See also http://pypi.python.org/pypi/cram (which has a nice short description of it’s syntax — which is mostly the same as mercurial’s unified tests).

]]> Comment on Python optimization note: function calls are slow by Tweets that mention Python optimization note: function calls are slow « internal fragmentation -- Topsy.com http://www.selenic.com/blog/?p=656&cpage=1#comment-24 Tweets that mention Python optimization note: function calls are slow « internal fragmentation -- Topsy.com Mon, 26 Jul 2010 17:31:11 +0000 http://www.selenic.com/blog/?p=656#comment-24 [...] This post was mentioned on Twitter by alejolp and Yury Yurevich, Matt Mackall. Matt Mackall said: Some Python micro-optimization investigation: http://www.selenic.com/blog/?p=656 [...] [...] This post was mentioned on Twitter by alejolp and Yury Yurevich, Matt Mackall. Matt Mackall said: Some Python micro-optimization investigation: http://www.selenic.com/blog/?p=656 [...]

]]> Comment on Unifying the Mercurial wire protocol by mpm http://www.selenic.com/blog/?p=647&cpage=1#comment-23 mpm Fri, 16 Jul 2010 12:55:10 +0000 http://www.selenic.com/blog/?p=647#comment-23 Peter, I haven't looked at batching yet. It's doable, but it's slightly problematic on the client side which is using an imperative model: pack arguments, call, get results, then parse. Unserializing the client methods would mean either breaking them into two parts or wrapping some crazy coroutine around them. Peter, I haven’t looked at batching yet. It’s doable, but it’s slightly problematic on the client side which is using an imperative model: pack arguments, call, get results, then parse. Unserializing the client methods would mean either breaking them into two parts or wrapping some crazy coroutine around them.

]]> Comment on Mercurial Fellowship status for June by Mina R Waheeb http://www.selenic.com/blog/?p=650&cpage=1#comment-22 Mina R Waheeb Fri, 16 Jul 2010 08:47:28 +0000 http://www.selenic.com/blog/?p=650#comment-22 Amazing effort! Congratulations :) Amazing effort! Congratulations :)

]]>