Frank T. Villarreal, Jr. wrote: >Hello All! > >I am attempting custom modifications to Jetspeed and by default Turbine >code. I noticed that the lastest "release" of Jetspeed utilizes >turbine-2.2b1-20011123.jar. When I go to retrieve Turbine's source from CVS >... I'm getting Turbine's HEAD code ... does anyone know the CVS module name > Try cvs update -D "2001-11-23" after checkout to get this dated version.
I'm not sure if you can specify this argument straight into the checkout, it used to be impossible due to a bug. Even when there is no branch, you can do this. The date spec is in the local timezone, and I'm not completely sure about granularity of time, but it should be enough given the activity level in turbine-2. The change is sticky, so you should "update -A" to get HEAD again. > >for the Turbine source code associated with the aforementioned jar ... I >would like to make sure my Turbine modifications are in sync with the >Jetspeed release's source code since they are inter-dependant. Please tell >me there is a snapshot module of the source code for that jar ... or am I >out of luck? If I am out of luck, can I make a humble suggestion? In future >releases of Jetspeed, can we make sure there is a CVS Turbine source code >module available for the jar that is included with Jetspeed? Just a thought >... it would probably save a lot of headaches for developers trying to >modifiy the code. Anyway, thanks for any help! > cvs keeps track of every single change in turbine code. It means that you can recover any atomic change (each commit is considered to be atomic) in the code base, even use "update -D yesterday" or update "-D '1 month ago'", according to man pages. It is very handy to get diffs, for instance, all diffs in the week. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
