I don't know how many Mercurial users are on this site, but if you do use Mercurial, you may have heard of the Mercurial killer extension, Evolve, which is eventually planned to be in Mercurial core.
There is a new user guide out now. You can see it at Evolve: User Guide
As you can see, this guide has 12 figures. It seems to me these figures are crying out for some TikZ love.
So, I thought it would be nice if the community could get together and create figures for this guide. Once these exist, creating more figures would probably be easier. I realise this is not what this site is customarily used for, but since it is in a good cause (a widely used piece of free software) perhaps people could stretch a point. Once produced, it would not be difficult to merge these figures into the user manual.
I was thinking that we could mark everything community wiki, and each answer could be for one figure.
Here is the source code repository for Evolve on Bitbucket.
Here the figures. The figures that correspond to the figures in the user guide are of the form figure-ug{i}.svg, where i = 1,...,12.
UPDATE: Looks like I jumped the gun a bit here. It was pointed out to me that the maintainers may not be willing to accept TikZ figures, even if produced. I've written to the mercurial devel mailing list, and I'll update this if and when I hear from them. If they are not willing to accept the figures, there seems little point in pursuing this.
UPDATE 2: As people here predicted, Pierre-Yves was not ehthusiastic about this. Evolve is his baby. Here are some extracts from yesterdays #mercurial IRC channel. Given these comments, it doesn't look likely this is going to happen, though it came up during the chat (details omitted) that another Mercurial developer (smf in the chat transcript below) had independently suggested the same thing, and said he had done some preliminary TikZ work on the diagrams. However, I've not seen this work yet. I'll leave this question open for now, if that is Ok. If not, let me know.
12:27 < marmoute> faheem: not super enthousiastic at the tikz idea
12:32 < faheem> marmoute: so i heard via durin42. are you familiar with it?
12:39 < marmoute> faheem: I've some exposure to it. but I fill like it going
to be a pretty high entry barrier for contributors. Both from a skill
perspective and a build dependency one
12:40 < faheem> marmoute: Ok. The build dependency bit can be automated,
though
12:41 < faheem> anyway, the tex.sx people predicted it wouldn't fly.
12:41 < faheem> as you could see from the comments there.
12:42 < marmoute> faheem: the dependency bit can be automated on proper
operating system with proper dependency management.
12:43 < marmoute> (and I kind of hate when I've to download a fw GB of latex
package on crappy hotel wifi when I do a dist-upgrade)
12:44 < faheem> marmoute: is there some problem in using "proper operating
system with proper dependency management"?
12:44 < smf> faheem: I have a fork of mutable-history that implements TikZ
12:44 < marmoute> [...] I would like to have a a nice and automated way to
generated the diagrams. But I feel like we did not saw anything
signicantly better than svg.
12:46 < marmoute> I can still be convinces de the tkz is better and less
troubles. but is has to be amazing
12:46 < faheem> marmoute: tikz is pretty amazing
12:47 < smf> TikZ is da bomb.com
12:48 < faheem> marmoute: tikz is also quite automated. yes, it is a good bit
of extra overhead
12:51 < marmoute> what could convince me is a easy a lightweight syntax to
write the kind of diagram we need in evolve. The exchange test is a
good benchmark
