Steve Borho <[email protected]> wrote: > On Fri, Jun 4, 2010 at 4:38 AM, Stefan Haller <[email protected]> wrote: > > Hi, > > > > Suppose I have a commit graph like this: > > > > o 6 > > | > > o 5 > > |\ > > | o 4 > > | | > > o | 3 > > | | > > |/ > > o 2 > > | > > o 1 > > > > > > Now, with changeset 4 selected in the annotate tab, I select "Annotate > > parent". I would expect it to take me to changeset 2, because that's > > the parent of 4; however, it takes me to changeset 3, which is an > > unrelated commit. > > > > I have the impression that "Annotate parent" always simply takes me to > > the line below the current one in the list. Am I missing something? > > Nope. > > > Also, in the case of a merge, wouldn't it make sense to provide both > > "Annotate 1st parent" and "Annotate 2nd parent" commands? > > Yep. > > Feel free to open enhancement requests for both.
Thanks. I added the first one as a comment to issue 1269, which seems related; hope that's ok. The second would depend on the first one, and I didn't see a "depends on" feature in the bug tracker, so I didn't file it yet. It's also the less important one for me personally. -- Stefan Haller Berlin, Germany http://www.haller-berlin.de/ ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
