From: LEE Sau Dan <danlee@informatik.uni-freiburg.de>
Subject: Re: problem with diffs in cvs
Date: 08 Jun 2004 23:50:12 +0200 [thread overview]
Message-ID: <m3vfi1afe3.fsf@mika.informatik.uni-freiburg.de> (raw)
In-Reply-To: 878yeyin6y.fsf@tfdpc12.tfd.chalmers.se
>>>>> "Fabian" == Fabian Braennstroem <f.braennstroem@gmx.de> writes:
Fabian> Hello, I have somehow problems to show the diffs for my
Fabian> cvs-files with pcl-cvs. Using the interactive diff (or
Fabian> other diffs)
Interactive diff? Is it ediff?
Fabian> I don't see any differences at all, but the log file
Fabian> shows clearly the different revisions with my logs which I
Fabian> check in with 'C-x v v'.
You need to spend some time with the manual of the ediff: C-h i d m
ediff <RET>
Basically, you use <SPACE> and <BACKSPACE> to navigate the difference
in ediff, and press 'q' to quit.
--
Lee Sau Dan 李守敦 ~{@nJX6X~}
E-mail: danlee@informatik.uni-freiburg.de
Home page: http://www.informatik.uni-freiburg.de/~danlee
next parent reply other threads:[~2004-06-08 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <878yeyin6y.fsf@tfdpc12.tfd.chalmers.se>
2004-06-08 21:50 ` LEE Sau Dan [this message]
2004-06-09 13:54 ` problem with diffs in cvs Fabian Braennstroem
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3vfi1afe3.fsf@mika.informatik.uni-freiburg.de \
--to=danlee@informatik.uni-freiburg.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).