On Wed, 13 Mar 2013 15:50:03 +0100, Peer Sommerlund wrote: > On 13 March 2013 13:38, Pierre Retoille <[email protected]> wrote: > > I get a strange commit tree displayed in tortoisehg. > > As it is difficult to describe I have place an image online that shows it. > > Please see here: > > http://www.roodle.de/album/key/m9mx3u4mefq82gthmy2t/id/7794/photo/id/279736/size/big/cachecontrol > > > > As far as I understand every committed version is represented by a dot on > > the > > commit tree. > > But as you can see on the image, in this case there are branches that end > > without a dot. > > The green branch on the image has no anchestor. I suspect there appeared > > an error during a commit. > > > > Please would somebody point out to me what this means and how to fix it. > > > > I am not sure if this is a bug or if I made something wrong. > > > > The version I use is tortoisehg 2.7.1 and mercurial 2.5.2 > > > > thank you very much > > Pierre > > > > This looks very much like a bug. > > What strikes me as odd is that rev 479 has two parents, but they are both > rev 474, as well as two children (both are rev 480). That should never > happen in real life, but if it did you would get the graph shown. > > Have you been using MQ or some other extension to modify history? > > Does this go away if you restart TortoiseHg?
Last year, my colleague did the same thing, a merge commit of single parent. He said he did pull, update and merge using TortoiseHg on Windows. I tried to reproduce the problem, but it never happen since then. Regards, ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
