[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: question regarding cvs history
From: |
Kaz Kylheku |
Subject: |
Re: question regarding cvs history |
Date: |
Wed, 12 Sep 2001 22:47:45 GMT |
User-agent: |
slrn/0.9.6.3 (Linux) |
In article <address@hidden>, Mark Lancisi wrote:
>I need to find out which modules have been committed on a branch tag I
>created 1 week ago. Getting this sort of info from the mainline is not
>particularly difficult, but I'll be damned if I can figure out how to get it
>for branches...
>
> I don't see any mention of how to show history of branches in any cvs
>history help or FAQ I have found . Is cvs history the correct command to use
>to get this info (and if so, what is the magic) OR is there some other
>command I should use ( or file I should look at...)
To see a commit history, use cvs log. The output format of cvs log is
not particularly well arranged for reconstructing a commit history, but
the information is there. Karl Fogel's cvs2cl Perl script can rearrange
the contents into a ChangeLog file or XML. It will figure out what
changes were commited together, and group them together with the log
message and spit them out in reverse chronological order.
I hacked a version of it which will produce the changelog as a set of
static web pages: the history is in the index page. In each entry, you
can click on files and view the diffs, which are also generated before
hand as static web pages.