backing up my repositories, anything special needed?
Govind Salinas
govindsalinas at gmail.com
Mon Aug 13 10:00:45 CDT 2007
Hi,
I have been evaluating using a DSCM over Perforce myself for work,
primarily so I could more easily collaborate with my co-workers (this
of course implies getting them to use it too). It really has come
down to git vs hg. I like hg because it is so much better supported
on windows (git is making progress but it is still not complete
support) and the lack of maintenance needed. Unfortunately I am left
with git that has good p4 support (can do go both ways) and hg which
has good windows support.
I have seen comments like these while browsing the hg archives and it
seems like a lot of overhead to manually take the diffs from one place
and then apply them to another. Even more so for the project that I
want because the p4 client I use is very complex, has a lot of
peripheral stuff in it and large(about 4G) binary SDKs that are copied
from a fileshare before you can build it. So keeping two copies of
the client around is rather cumbersome.
Does the list have any suggestions for me while I am still in the
evaluation phase?
Thanks,
Govind.
On 8/12/07, Giorgos Keramidas <keramida at ceid.upatras.gr> wrote:
> On 2007-08-12 13:10, Dustin Sallings <dustin at spy.net> wrote:
> > At work, we use perforce. I sync perforce -> hg and do all of my
> > work in my hg tree with mq. I pull changes straight out of mq to go
> > back into perforce and then delete them from mq and let them come
> > back in through hg.
>
> Interesting. This is actually a *very* good description of how I use
> MQ at work too (where I also have to use Perforce).
>
> I wonder how many people use Mercurial to get a faster, distributed
> "overlay" on top of Perforce (or another centralized SCM) :-)
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
More information about the Mercurial
mailing list