From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: spearce@spearce.org
Cc: git@vger.kernel.org, Robin Rosenberg <robin.rosenberg@dewire.com>
Subject: [EGIT PATCH 0/3] Show all changes files in the same compare editor
Date: Sat, 10 Jan 2009 02:14:34 +0100 [thread overview]
Message-ID: <1231550077-1057-1-git-send-email-robin.rosenberg@dewire.com> (raw)
Hereby I ressurrect some of the goodness the old compare editor had,
by enabling it to show all changes in the same compare editor so one
can browse back and forth using Ctrl-. and Ctrl-, instead of having
to click on each changed file.
Question: Do we need the filediff viewer AND the compare editor. We
used to have the compare editor update automaticall when one switched
revision in the history pane.
-- robin
Robin Rosenberg (3):
Support viewing all changes in a single compare editor
Present type of change with file revision in diff viewer
Present full name of file revision
.../core/internal/storage/GitFileRevision.java | 5 +-
.../ui/internal/history/CommitFileDiffViewer.java | 40 +++++++--
.../internal/history/FileDiffContentProvider.java | 11 ++-
.../ui/internal/history/FileDiffLabelProvider.java | 49 +++++++++--
.../spearce/egit/ui/internal/history/RevDiff.java | 91 ++++++++++++++++++++
5 files changed, 179 insertions(+), 17 deletions(-)
create mode 100644 org.spearce.egit.ui/src/org/spearce/egit/ui/internal/history/RevDiff.java
next reply other threads:[~2009-01-10 1:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 1:14 Robin Rosenberg [this message]
2009-01-10 1:14 ` [EGIT PATCH 1/3] Support viewing all changes in a single compare editor Robin Rosenberg
2009-01-10 1:14 ` [EGIT PATCH 2/3] Present type of change with file revision in diff viewer Robin Rosenberg
2009-01-10 1:14 ` [EGIT PATCH 3/3] Present full name of file revision Robin Rosenberg
2009-01-10 1:28 ` Robin Rosenberg
2009-01-12 16:54 ` [EGIT PATCH 1/3] Support viewing all changes in a single compare editor 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=1231550077-1057-1-git-send-email-robin.rosenberg@dewire.com \
--to=robin.rosenberg@dewire.com \
--cc=git@vger.kernel.org \
--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).