Discussion:
[BitPim-devel] Re: [bitpim-cvs-checkins] bitpim com_audiovoxcdm890 0.py,1.16,NONE com_brew.py,1.67,NONE com_gsm.py,1.1,NONE com_lg.py,1.3 1,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_lgpm325.py,1.3,NONE com_lgt
Joe Pham
2006-03-02 00:18:27 UTC
Permalink
Joe,
The intention was that I would do this moving while making the CVS
to Subversion change. Since CVS can't track files moving, this
discards the history for all the files!
Sorry Roger, I misunderstood. I'll back out the changes.

-Joe Pham




_____________________________________________________________________
Call Anyone, Anytime, Anywhere in the World - FREE!
Free Internet calling from NetZero Voice
Visit http://www.netzerovoice.com today!
Roger Binns
2006-03-02 01:55:25 UTC
Permalink
Post by Joe Pham
Sorry Roger, I misunderstood. I'll back out the changes.
The best thing to do at the moment is not make any changes to
any more code. I think I can undo this in the conversion
script. Failing that I have a snapshot of the CVS repository
from last night. I can do the conversion from that and
any changes made today will have to be redone in Subversion.

I am very happy with the Subversion conversion. Effectively
it rewrites history pretending that things had always been
organized the way it outputs. The script does the following:

- Removes all branches (the last branches were for 0.5 and 0.6
any)
- For files that have been cvs deleted, makes it like they
never existed
- For binary files, removes all revisions except the most
recent (they are generally made from something else so
earlier revisions don't matter)
- For the online help, removes all old revisions except the
most recent. Many of the old revisions were just the
help id numbers changing.
- Renames the web pages module, moves the helpblocks to
web conversion into a subprojects space
- I will add moving the phones into a subdirectory and the
larger reorganization (top level contains src, help, etc
rather than zillions of files)

I propose we do the following:

- Do the CVS to Subversion conversion using CVS as of last
night
- Load it up onto SourceForge this evening. It will not
work perfectly as some small changes will need to be
made due to reorganization
- I don't believe there will be any structural issues, but
people should look for them immediately. If issues are
found, the Subversion repository will be removed and
replaced with a fixed version
- Any CVS changes made today, as well as any Subversion
changes made before a repository replacement will have
to be re-applied.

Roger
Simon C
2006-03-02 03:59:49 UTC
Permalink
Post by Roger Binns
- Do the CVS to Subversion conversion using CVS as of last
night
- Load it up onto SourceForge this evening. It will not
work perfectly as some small changes will need to be
made due to reorganization
- I don't believe there will be any structural issues, but
people should look for them immediately. If issues are
found, the Subversion repository will be removed and
replaced with a fixed version
- Any CVS changes made today, as well as any Subversion
changes made before a repository replacement will have
to be re-applied.
Seconded.
I'm looking forward to using this later tonight :)

Simon
Roger Binns
2006-03-02 05:14:30 UTC
Permalink
Post by Simon C
Seconded.
I'm looking forward to using this later tonight :)
If you are awake and in my time zone :-)

Roger

Loading...