From: "Roger C. Soares" <rogersoares@intelinet.com.br>
To: "Shawn O. Pearce" <spearce@spearce.org>,
Robin Rosenberg <robin.rosenberg@dewire.com>
Cc: git@vger.kernel.org
Subject: Re: faster egit history page and a pure java "gitk"
Date: Mon, 24 Mar 2008 10:33:23 -0300 [thread overview]
Message-ID: <47E7ADA3.2060906@intelinet.com.br> (raw)
In-Reply-To: <20080324092726.GQ8410@spearce.org>
Shawn O. Pearce escreveu:
> OK, so I decided a few weeks back that the history page was not fast
> enough. I think I've spent the past 3 weeks writing true revision
> machinary for jgit, and now connecting it up to a UI visualizer.
>
> git://repo.or.cz/egit/spearce.git plotter
>
> The history page has been completely replaced. I saw Roger has
> some patches against the current history page. :-|
>
Hi Shawn. This is awesome, I can't wait to see this integrated in the
main repo :)
I don't spend much time working on egit so I usually take a while to
make small things, but I can certainly merge my patches on top of yours.
Robin, how should I proceed, resend all my patches from the weekend on
top of Shawn's tree?
[]s,
Roger.
next prev parent reply other threads:[~2008-03-24 13:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 9:27 faster egit history page and a pure java "gitk" Shawn O. Pearce
2008-03-24 13:33 ` Roger C. Soares [this message]
2008-03-24 14:10 ` Robin Rosenberg
2008-03-25 4:43 ` Shawn O. Pearce
2008-03-25 12:33 ` Roger C. Soares
2008-03-24 14:06 ` Robin Rosenberg
2008-03-25 5:10 ` Shawn O. Pearce
2008-03-24 14:31 ` faster egit history page and a pure java "gitk" so Robin Rosenberg
2008-03-25 4:48 ` Shawn O. Pearce
2008-03-25 5:07 ` faster egit history page and a pure java "gitk" Roger C. Soares
2008-03-25 5:36 ` Shawn O. Pearce
2008-03-25 8:09 ` Shawn O. Pearce
2008-03-25 13:46 ` Roger C. Soares
2008-03-25 19:48 ` Robin Rosenberg
2008-03-26 1:37 ` Roger C. Soares
2008-03-26 4:52 ` Shawn O. Pearce
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=47E7ADA3.2060906@intelinet.com.br \
--to=rogersoares@intelinet.com.br \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg@dewire.com \
--cc=spearce@spearce.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).