Hi Larry,
I've been reading this thread, and I think the CVS repository you set up
is a great service. I have a request to improve the quality of the data.
If you want to skip straight to the suggestion, goto SUGGESTION.
I am maintainer of a handy GPLed utility called 'cvsps' (plug:
http://www.cobite.com/cvsps) which extracts 'patchset' information from a
cvs repository by parsing the 'cvs log' output. It attempts to recreate a
commit as a single atomic action, and all the branch and tag gook that
goes with it.
It's a read-only tool that I find useful to see what is going on in a cvs
repository.
Back to you: I've looked at the CVS log output from your repository, and
had my program parse it back into 'patchsets' but it's not doing a great
job because the log messages from separate parts of the commit are
different.
This is fine, because I can easily write a 'hack' to look explicitly for
the '(Logical change x.yyyyy)' text to group individual file commits back
into patchsets.
But this text is missing from the 'main' file commit (to the ChangeSet
file) that has the BKrev: tag in it.
SUGGESTION:
Put the '(Logical change x.yyyy)' text into EVERY log message that is a
port of the logical change, including the 'main' commit to the ChangeSet,
that commit has the BKrev: in it (it's missing from this one file's log
message).
Then I can make a '--bk' hack to my program to use this 'key' to recreate
the commits.
Let me know what you think,
David
-- /==============================\ | David Mansfield | | lkml@dm.cobite.com | \==============================/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Mar 15 2003 - 22:00:35 EST