"Nicola Ken Barozzi" <[EMAIL PROTECTED]> wrote:
>
> Jeff Turner wrote, On 27/02/2003 15.22:
>> On Thu, Feb 27, 2003 at 02:30:57PM +0100, Carsten Ziegeler wrote:
>>
>>> So, now we all (at least those participating) have the same understanding
>>> and we can start a vote:
>>>
>>> A cocoon version is defined as MAJOR.MINOR.PATCHLEVEL
>>>
>>> - One repository for each MAJOR.MINOR combination
>>
>>
>> This would remove the facility of typing "cvs update -j <tag>" for
>> synching updates across minor releases (eg 2.0.x and 2.1).
>
> My impression was that we should focus now on 2.1 anyway, so making it
> harder to synch could be a bonus for us, going with 2.1 and stopping to
> use 2.0.x as an excuse ;-)
Well, but if you really want to do that, there is a way to: for example, if
in cocoon-2.0 I want to get the "build.xml" file that someone just committed
to "cocoon-2.1" (so, in another repository) and which has version number
"1.321", what I simply do is:
~ # cd cocoon-2.0
~/cocoon-2.0 # cvs co -r 1.321 -p xml-cocoon2/build.xml > build.xml
~/cocoon-2.0 # cvs cvs commit -m "Merged from cocoon-2.1 version 1.321"
~/cocoon-2.0 # cd ..
~ #
All done... Instead of using "update -j [tag]" you use
"checkout -r [tag] -p [file] > [local]"
Slightly more complicated, but I have a script doing it! :-)
Pier
