git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mark Levedahl" <mlevedahl@gmail.com>
To: "Paul Mackerras" <paulus@samba.org>
Cc: "Mark Levedahl" <mdl123@verizon.net>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH] gitk - dont warn when deleting synonym for current head
Date: Mon, 13 Aug 2007 09:22:24 -0400	[thread overview]
Message-ID: <30e4a070708130622l7558230cpb870378aeba537fb@mail.gmail.com> (raw)
In-Reply-To: <30e4a070708130604g5b848b2fm4b42e145384c0ba4@mail.gmail.com>

On 8/13/07, Mark Levedahl <mlevedahl@gmail.com> wrote:
> 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

      reply	other threads:[~2007-08-13 13:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-12 21:03 [PATCH] gitk - dont warn when deleting synonym for current head Mark Levedahl
2007-08-12 23:44 ` Paul Mackerras
2007-08-13  1:10   ` Mark Levedahl
2007-08-13  1:51     ` Mark Levedahl
2007-08-13  3:52       ` Paul Mackerras
2007-08-13 13:04         ` Mark Levedahl
2007-08-13 13:22           ` Mark Levedahl [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=30e4a070708130622l7558230cpb870378aeba537fb@mail.gmail.com \
    --to=mlevedahl@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mdl123@verizon.net \
    --cc=paulus@samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).