Hi David, On Fri, Dec 30, 2005 at 08:15:40PM +0200, David Fraser wrote: > > I'm trying to find out what's involved in certain CWSs. Using EIS I can > see the issues attached to a CWS but not what actual files have been > changed and the changes made.
You can see the files once the cws is integrated. > So what I'd really like to do is get a patch that corresponds to all the > changes made in that CWS. Just update your tree to that CWS. (I always create a shadow-tree of pristine sources and update that copy to a certain cws. This way you only have to do "find . -type f" to see what files did actually change. > The cws tools (and the ooo-build enhancement cws-extract) should be able > to do that. You can do that even without the tools. cvs can do (r)diffs between different branches/revisions as well. It might be not as efficient since it operates on all the files and not only on those that actually were changed, but since the information is not available until the cws is integrated, the cwstools would have to do the same thing anyway. > [...] > 2) In the mean time, it would be nice if either EIS or some other web > site provided such patches. What for? Just to be lagging behind all the time? > They need not be generated dynamically, a > nightly run of cws-extract would be great and they could offer static > links to the patches. Again: What for? > What do people think? I don't think this makes sense. If you're interested in the patches, you probably have the sources already. So just checkout that particular cws you're interested in or let cws create a patch/diff for the relevant modules and you're done. ciao Christian -- NP: Paradise Lost - Colossal Rains --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
