Re: [PATCH] gitk - dont warn when deleting synonym for current head
- From
Mark Levedahl <mlevedahl@gmail.com>
- Date
- Aug 13, 2007, 13:22 UTC
- Message-ID
- <30e4a070708130622l7558230cpb870378aeba537fb@mail.gmail.com>
- In-Reply-To
- <30e4a070708130604g5b848b2fm4b42e145384c0ba4@mail.gmail.com>
On 8/13/07, Mark Levedahl <mlevedahl@gmail.com> wrote:
Show 8 quoted lines
> On 8/12/07, Paul Mackerras <paulus@samba.org> 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