From: "Shawn O. Pearce" <spearce@spearce.org>
To: "Roger C. Soares" <rogersoares@intelinet.com.br>
Cc: git@vger.kernel.org, robin.rosenberg@dewire.com
Subject: Re: [EGIT PATCH 1/3] FindToolbar port to the new history page.
Date: Mon, 7 Apr 2008 01:19:08 -0400 [thread overview]
Message-ID: <20080407051908.GS10274@spearce.org> (raw)
In-Reply-To: <1207518109-4174-1-git-send-email-rogersoares@intelinet.com.br>
"Roger C. Soares" <rogersoares@intelinet.com.br> wrote:
> This is a port from the find toolbar to the new history page.
> It is replacing the current highlight flag in order to have the
> find feature back but most of the code from the toolbar shall be
> replaced to make use of the new infrastructure added into jgit
> (RevFlag and RevFilter).
...
> I'm reseding the toolbar port with the fixes for the items you mentioned.
> It's on top of 009f11e2c8971b6053, don't know if it would have been better
> to rebase it, just let me know.
Well, I just rebased my entire tree, and then plopped your four
patches (these three plus 009f) on top of it. So no need to rebase.
There was a very minor merge conflict, easily fixed, no worries.
> Patch 3/3 is something I've come up to remove the Map hit in the paint
> method. As you said you were going to revisit the jgit API soon I didn't
> want to do something too elaborated that will be dumped soon. I'm
> manipulating RevFlags directly from the find toolbar, so if you don't
> like just ignore it.
Its better. I'd like to be able to use more of RevFilter in the
search, but as you pointed out support isn't all there yet.
I'm taking in this series as is. We can improve on it further later.
Thanks.
--
Shawn.
prev parent reply other threads:[~2008-04-07 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 21:41 [EGIT PATCH 1/3] FindToolbar port to the new history page Roger C. Soares
2008-04-07 5:19 ` Shawn O. Pearce [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=20080407051908.GS10274@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg@dewire.com \
--cc=rogersoares@intelinet.com.br \
/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).