From: A Large Angry SCM <gitzilla@gmail.com>
To: Paul Mackerras <paulus@samba.org>
Cc: git@vger.kernel.org
Subject: Re: any problems with new branch of gitk?
Date: Sun, 05 Mar 2006 15:16:06 -0800 [thread overview]
Message-ID: <440B7136.2000809@gmail.com> (raw)
In-Reply-To: <17419.24973.402408.237865@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
> I'm planning to pull the `new' branch of the gitk repository into the
> master branch, making the new version of gitk the standard version
> that will go into the git.git repository. As far as I know the new
> version does everything the old version does. Does anyone know of any
> problems with the new gitk that weren't in the old one?
I don't know if the old version has this problem but the new version
does not have a "busy" pointer while it's waiting for a merge diff. Take
a look at the ACPI mega(octo)pus merge that happened in January.
next prev parent reply other threads:[~2006-03-05 23:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 22:09 any problems with new branch of gitk? Paul Mackerras
2006-03-05 23:16 ` A Large Angry SCM [this message]
2006-03-06 20:23 ` Alex Riesen
2006-03-15 11:18 ` Paul Mackerras
2006-03-15 13:00 ` Alex Riesen
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=440B7136.2000809@gmail.com \
--to=gitzilla@gmail.com \
--cc=git@vger.kernel.org \
--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).