Re: [p4] restoring DVCS and using classic Depots

Posted on behalf of forum user 'Sambwise'.

This sounds like a lot of reinventing the wheel -- if you've got a setup
that works for you, go for it, but I'd recommend to anyone else who has
found this post via Google and is tempted to use it as a "getting
started" guide that they read the official docs first (or post here with
questions).  All the manual effort to back stuff up to the central
server by checking in the db.* files should be replaceable by a simple "p4
push" command, for example -- if you want to push more than the
"main" stream all you need to do is change the remote
spec.  If everything is pushed up to the central server, you can
reconstruct your local DVCS with a "p4 clone" command.



Quote
>   When I tried to access it (either command line or with P4V) I would get a "no client" access error because the client specification had been lost.    
If you had a backup of the db.* files, it's pretty unlikely that you lost
the client and nothing else.  I'm guessing you just lost the
client *setting* because the old p4config.txt file wasn't backed up, and
because "p4 init" generates a hard-to-remember client
ID?  If you run into this again, just run "p4 clients"
against your server to see what the client is (there'll probably only be one
since in a typical DVCS setup there's only one client), and then set your
client name to that value.

Long before p4 DVCS existed I did have scripts to copy changes between servers,
including doing wild stuff like using sync/submit to synchronize db records in
journal form.  Trust me, just using the DVCS stuff is way
better.   :)



--
Please click here to see the post in its original format:
  http://forums.perforce.com/index.php?/topic/5490-restoring-dvcs-and-using-classic-depots
_______________________________________________
perforce-user mailing list  -  [email protected]
http://maillist.perforce.com/mailman/listinfo/perforce-user