Gitx GitX

Comments and changes to this ticket

• 

  Pieter de Bie March 23rd, 2009 @ 11:50 PM

  • State changed from “new” to “open”

  Hmm, I thought I tested for that. Oh well, I'll keep it open. Thanks!

• 

  Pieter de Bie March 29th, 2009 @ 12:43 AM

  I'm sorry, I don't really know how to replicate this. Is this a public repository?

• 

  Elia Schito March 30th, 2009 @ 10:02 AM

  nope, it isn't public, and even worst I've rewritten the repo history and now there's only one branch (I had the first half of the repo history in CVS and that image was in the middle of merging)... btw I'll try to replicate somehow the bug and the I'll try to give the bugged repo to you...

• 

  Elia Schito March 30th, 2009 @ 10:35 AM

  Trying to recall from memory the status of that history I think the problem was something like this:

  This is what should have rendered:

  
    |
    |
    o Commit ABC
    |\         
    | |         
    | o Commit BC'
    | |         
    | o Commit BC 
    | |         
    | | o Commit B''       
    | |/|
    | o | Commit C''
    | | |
    | | o Commit B'
    | | |
    | o | Commit C'
    | | |
    | o | Commit C (this branch has no ancestors!)                                          
    |   |
    |   o Commit B 
    | /
    |/
    o Commit A
    |
  

  And this what has been rendered:

  
    |
    |
    o Commit ABC
    |\         
    | |         
    | o Commit BC'
    | |         
    | o Commit BC 
    | |         
    | | o Commit B''       
    | |/|
    | o | Commit C''
    | | |
    | | o Commit B'
    | | |
    | o | Commit C'
    | | |
    | o | Commit C (this branch has no ancestors!)                                          
    |
    | |
    | o Commit B 
    |/
    o Commit A
    |
  

  Don't know if it'll be helpful, in my (very humble) opinion it has to do with that new branch without ancestors...

  Ask me if you have further questions, (and thanks for this cool software ;)

• 

  Pieter de Bie March 31st, 2009 @ 02:48 AM

  Yup, this has definitely got to do with ancestorless commits. I tried to create a testcase for this, but somehow the guilty commit was always in the rightmost line, which meant it wasn't reproducible. I guess I'll have to try harder..

• 

  Johannes Gilger September 12th, 2010 @ 03:04 PM

  • Milestone order changed from “0” to “0”

  Any progress on this one? I don't have many ancestorless branches, and they do always end up in the rightmost column, like Pieter described.