From: Paul Mackerras <paulus@samba.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: David Aguilar <davvid@gmail.com>,
Tim McCormack <cortex@brainonfire.net>,
git@vger.kernel.org
Subject: Re: [PATCH] gitk: Rename 'tagcontents' to 'cached_tagcontent'
Date: Wed, 12 Sep 2012 22:37:56 +1000 [thread overview]
Message-ID: <20120912123756.GA26593@bloggs.ozlabs.ibm.com> (raw)
In-Reply-To: <7v8vcffv93.fsf@alter.siamese.dyndns.org>
On Wed, Sep 12, 2012 at 02:25:28AM -0700, Junio C Hamano wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>
> > I've applied these two, on top of Paul's master branch at
> >
> > git://ozlabs.org/~paulus/gitk.git
> >
> > and tentatively queued in 'pu', but I would prefer to see it
> > eyeballed by and queued in his tree first.
> >
> > Thanks.
>
> Pinging Paul...
>
> The following changes since commit a135f214e371311f13807da637d492fd9642a2e3:
>
> gitk: Avoid Meta1-F5 (2012-04-25 13:44:31 +1000)
>
> are available in the git repository at:
>
> git://github.com/gitster/git da/gitk-reload-tag-contents
>
> for you to fetch changes up to 587277fea3bf3bfc4302480178bd88a277a69f05:
>
> gitk: Rename 'tagcontents' to 'cached_tagcontent' (2012-09-08 20:25:09 -0700)
Thanks, pulled and pushed out. I had one other commit queued up, so
if you pull from git://ozlabs.org/~paulus/gitk.git you will get that
plus a merge.
Paul.
prev parent reply other threads:[~2012-09-12 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 18:17 gitk does not reload tag messages Tim McCormack
2012-09-07 3:08 ` David Aguilar
2012-09-07 5:18 ` Junio C Hamano
2012-09-08 19:03 ` [PATCH] gitk: Teach "Reread references" to reload tags David Aguilar
2012-09-08 19:53 ` [PATCH] gitk: Rename 'tagcontents' to 'cached_tagcontent' David Aguilar
2012-09-09 5:11 ` Junio C Hamano
2012-09-12 9:25 ` Junio C Hamano
2012-09-12 12:37 ` Paul Mackerras [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=20120912123756.GA26593@bloggs.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=cortex@brainonfire.net \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).