From: Kai Grossjohann <kai.grossjohann@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: PCL-CVS: more diff options
Date: Thu, 25 Sep 2003 23:13:32 +0200 [thread overview]
Message-ID: <86eky41shv.fsf@slowfox.dyndns.org> (raw)
In-Reply-To: <jwv7k3whhif.fsf-monnier+emacs/devel@vor.iro.umontreal.ca> (Stefan Monnier's message of "25 Sep 2003 14:08:24 -0400")
Stefan Monnier <monnier@IRO.UMontreal.CA> 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
> .#<file>.<rev>.
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/<something>
> 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.)
prev parent reply other threads:[~2003-09-25 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 7:27 PCL-CVS: more diff options Kai Großjohann
2003-09-25 18:08 ` Stefan Monnier
2003-09-25 21:13 ` Kai Grossjohann [this message]
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=86eky41shv.fsf@slowfox.dyndns.org \
--to=kai.grossjohann@gmx.net \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.