From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kai Grossjohann Newsgroups: gmane.emacs.devel Subject: Re: PCL-CVS: more diff options Date: Thu, 25 Sep 2003 23:13:32 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <86eky41shv.fsf@slowfox.dyndns.org> References: <4036.1064474857@www54.gmx.net> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1064788873 22996 80.91.224.253 (28 Sep 2003 22:41:13 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 28 Sep 2003 22:41:13 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Sep 29 00:41:11 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1A3kE3-0003El-00 for ; Mon, 29 Sep 2003 00:41:11 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1A3kE3-0008Ap-00 for ; Mon, 29 Sep 2003 00:41:11 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.22) id 1A3kCU-0001wy-9P for emacs-devel@quimby.gnus.org; Sun, 28 Sep 2003 18:39:34 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.22) id 1A3kBp-0001lA-Io for emacs-devel@gnu.org; Sun, 28 Sep 2003 18:38:53 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.22) id 1A3kBm-0001jg-RO for emacs-devel@gnu.org; Sun, 28 Sep 2003 18:38:51 -0400 Original-Received: from [213.165.64.20] (helo=mail.gmx.net) by monty-python.gnu.org with smtp (Exim 4.22) id 1A3kBl-0001hS-Rg for emacs-devel@gnu.org; Sun, 28 Sep 2003 18:38:50 -0400 Original-Received: (qmail 2259 invoked by uid 65534); 28 Sep 2003 22:12:05 -0000 Original-Received: from p508E16E0.dip.t-dialin.net (EHLO slowfox.dyndns.org) (80.142.22.224) by mail.gmx.net (mp010) with SMTP; 29 Sep 2003 00:12:05 +0200 X-Authenticated: #361006 Original-Received: by slowfox.dyndns.org (Postfix, from userid 1001) id 09B264493; Thu, 25 Sep 2003 23:13:32 +0200 (CEST) Original-To: Stefan Monnier In-Reply-To: (Stefan Monnier's message of "25 Sep 2003 14:08:24 -0400") User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (berkeley-unix) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:16740 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:16740 Stefan Monnier writes: >> I am in the habit of doing M-x cvs-update RET in the morning. Say that >> I then see that the file foo has been updated. Now what I routinely want >> to know is what has changed by this update. > >> WIBNI PCL-CVS offered a convenient way to see this? > > The problem is that CVS doesn't really offer any way to do that. > If the file was locally modified, you can use the most recent > .#.. Well, just diffing the most recent two revisions would be fine, I think. Hm. Oh! What if the file has changed by more than one revision while I wasn't looking? Yes, indeed. Hm. > But otherwise, CVS doesn't remember which files were updated and > neither does it remember what was the previous revision number. Hm, yes. Hm. It should ;-) > PCL-CVS could try to do that, but for it to work even if you > exit/rerun PCL-CVS, we'd need to store it (in CVS/ > typically), which I'd rather avoid if possible). Hm. PCL-CVS would have to do "cvs status" first, so that it knows the state, right? Then a "cvs update" will say what has changed and so it can do the right diff. But if something was stored in CVS/foo, then maybe a history of updates would be nice. Then CVS could look in CVS/foo for when was the last update performed and then diff on the date. WDYT? > What I do instead is to use `dh' *before* updating. It also suffers from > problems, such as the race condition (someone might commit something > between the `dh' and the update). Ah, yes. Maybe I can remember to do that in the future. I wish people would just write ChangeLog entries like the good boys. But ChangeLog entries don't pay the rent and so I'll have to make do without them, I guess. (I am running cvs2cl from time to time, tho.)