On 8/13/07, Mark Levedahl <mlevedahl@xxxxxxxxx> wrote: > On 8/12/07, Paul Mackerras <paulus@xxxxxxxxx> wrote: > > It does load the full repository DAG - that's how it gets the > > information for the Precedes:, Follows: and Branch(es): fields in the > > commit display. It's true that that can be turned off, though, and in > > that case an "are you sure" dialog would be appropriate. > > > > Paul. > Double groan - I hit the wrong key (send rather than abort) with a partially written incorrect message. Drat. I was fooled as the "Precedes:" entry is blank if I do, for instance: git checkout -b foo master~1 gitk even though HEAD=foo which precedes master. However, master shows up in the list of branches containing the commit. So yes, I see that gitk has the full DAG available and could therefore generate a useful warning when deleting a branch would leave dangling commits. Mark - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
