From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: "Roger C. Soares" <rogersoares@intelinet.com.br>
Cc: git@vger.kernel.org
Subject: Re: [EGIT PATCH] Refresh history when "Refresh" is clicked in the history viewer.
Date: Sun, 24 Feb 2008 23:40:08 +0100 [thread overview]
Message-ID: <200802242340.09606.robin.rosenberg@dewire.com> (raw)
In-Reply-To: <1203895097-3742-1-git-send-email-rogersoares@intelinet.com.br>
måndagen den 25 februari 2008 skrev Roger C. Soares:
> ---
> .../src/org/spearce/egit/ui/GitHistoryPage.java | 8 ++++++--
> 1 files changed, 6 insertions(+), 2 deletions(-)
Looks ok, but what is the effect of refresh, besides possibly working around
other bugs? I would expect to to refresh with the selected resource as "filter",
but it doesn't.
-- robin
next prev parent reply other threads:[~2008-02-24 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 23:18 [EGIT PATCH] Refresh history when "Refresh" is clicked in the history viewer Roger C. Soares
2008-02-24 22:40 ` Robin Rosenberg [this message]
2008-02-25 0:07 ` Roger C. Soares
2008-02-25 0:11 ` Robin Rosenberg
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=200802242340.09606.robin.rosenberg@dewire.com \
--to=robin.rosenberg@dewire.com \
--cc=git@vger.kernel.org \
--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).