[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: capturing all aspects of a commit
From: |
Ralf S. Engelschall |
Subject: |
Re: capturing all aspects of a commit |
Date: |
Tue, 27 May 2003 19:30:07 +0200 |
User-agent: |
Mutt/1.4.1i |
On Sun, May 25, 2003, Akos Maroy wrote:
> I'd like to find a way to capture all change done by each commit
> operation. I'd like to maintain a database of commits, where I could
> list all the changes done by each commit (and have the possibility
> somehow to get sources prior to and after any commit).
> [...]
You can gather together the information during commit step-by-step the
same way OSSP Shiela (http://www.ossp.org/pkg/tool/shiela/) does it by
hooking into the various CVS info hooks. Or you can parse afterwards
the CVSROOT/history file as CVSTrac (http://www.cvstrac.org/) does.
There you also can identify a commit as a whole. If you need immediate
action, use the first attempt. If it is ok to update your database in
time intervals, use the second attempt.
Ralf S. Engelschall
address@hidden
www.engelschall.com
Re: capturing all aspects of a commit, Kaz Kylheku, 2003/05/25
Re: capturing all aspects of a commit,
Ralf S. Engelschall <=