Re: Re: [bitpim-cvs-checkins] bitpim com_audiovoxcdm8900.py,1.16,NONE com_brew.py,1.67,NONE com_gsm.py,1.1,NONE com_lg.py,1.31,NONE com_lgc2000.py,1.1,NONE com_lgg4015.py,1.7,NONE com_lglx5450.py,1.2,NONE com_lgpm225.py,1.1,NONE com_lg

> Should that be done for  the p_XXX.py files too as they are also derived
> files?

Yes, good catch.

Joe and I have been working on this.  We basically have 3 choices.
The final repository would look exactly the same with each choice
(ie if you do a checkout).  The difference is what history before
today would look like.

a) Empty
b) Present for current files, missing for files that were deleted 
   in the past.  For current files it would look like they have
   always been in their current place.  For binary files,
   generated files etc only the most recent revision would be
   in history.
c) The full history in all its details.  Also show how all the
   files/directories ended up in their new positions.

To get a true history you would always have to use CVS tools
for changes before today and SVN for changes after today.
CVS has different semantics and quirks than SVN.  That would
make a) seem sensible.

That said, the tools in TortoiseSVN are really nice.  So we
went for b so you could see relevant history using the TSVN
tools.

Roger


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642