backing up my repositories, anything special needed?

[Ben Hood]

>         mq does that, but it's a different issue.  I've had far more
> problems with the other side of this.  I knew a guy who wouldn't
> commit anything everything was ``done.''  This meant that his work
> wouldn't be seen by another human until it was time to ship.
> Integration is a *huge* pain when people do this as well.

Fair point, but I think that not pushing back your work because you
think you're completing the Sistine chapel is a slightly different
issue. Basically what I was asking was: Given a balanced approach to
commiting changesets (i.e. not too much, not too little), how can you
backup your local changed copy without being forced to make a
changeset then and there. I use MQ for my local changes, so if I could
do a qrefresh and then have that backed up, so it is resilient but
still a private change, that would be fine.

>         Personally, I use mq at work and when I check in code, it's often
> multiple distinct changesets that I send in around the same time.  mq
> lets me get things working while still allowing me to integrate
> changes made by other people and be working on distinct concepts.  I
> can't tolerate having work I've not checked in for more than a couple
> of days, so I at least check in and replicate my mq patches when a
> feature is taking me too long, or the rest of the team isn't ready
> for it.

That's interesting, I haven't looked at MQ in that way - does the
patch queue get synchronized when you do a hg push? Or are you how are
you backing up the patch queue?

Ben