From: Jakub Narebski <jnareb@gmail•com>
To: dtletmn <dtletmedn@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: Does CVS has a easy way to compare file with its previous version?
Date: Tue, 30 Jun 2009 05:36:04 -0700 (PDT) [thread overview]
Message-ID: <m3hbxxx5jk.fsf@localhost.localdomain> (raw)
In-Reply-To: <1e56aa11-735a-47f7-a273-5b6bf611f528@n11g2000yqb.googlegroups.com>
dtletmn <dtletmedn@gmail•com> writes:
> Hi,All,
>
> I am wondering if cvs has an easy way to compare a file with its
> previous version.
>
> In clearcase,I can use :
> cleartool diff -pred file.cc
>
> how can I acheive it in CVS?
> any help would be highly appreciated!
In CVS or in Git?
In CVS: "cvs diff -r <previous revision> <file>".
In Git: "git diff HEAD^ -- <file>".
Both assume that you want to compare with version from previous
commit.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-06-30 12:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 7:41 Does CVS has a easy way to compare file with its previous version? dtletmn
2009-06-30 11:32 ` Andreas Ericsson
2009-06-30 12:36 ` Jakub Narebski [this message]
2009-06-30 23:28 ` Paolo Bonzini
2009-07-01 1:18 ` Linus Torvalds
2009-07-02 18:04 ` Eric Raible
2009-07-03 6:39 ` Paolo Bonzini
2009-07-06 23:39 ` Eric Raible
2009-07-07 19:57 ` Paolo Bonzini
2009-07-01 0:29 ` dtletmn
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=m3hbxxx5jk.fsf@localhost.localdomain \
--to=jnareb@gmail$(echo .)com \
--cc=dtletmedn@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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