<div dir="ltr"><br><div class="gmail_quote">On Sun, Mar 13, 2011 at 13:25, Nick Coghlan <span dir="ltr"><<a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I'm experimenting with creating some local branches for things I'd<br>
like to work on during the sprints this week, and have a couple of<br>
questions about the associated workflow.<br></blockquote></div><br>The way to do this, IMHO, is just create a local clone and work on it. Then you can keep checking partial changes in without ever worrying about accidentally modifying the official repo. Especially if some of this work is experimental and bound to eventually be thrown away, I think it's a more flexible way to work than use MQ.<br>
<br>One thing to keep in mind though is backup. I may be paranoid, but I just can't do anything of importance on a local machine (especially a laptop) for any prolonged period of time without occasional backups. Thankfully, a Mercurial repo is about the best tool you have for backing things up - just remote clone it to bitbucket, google code or some place of your own and periodically push there.<br>
<br>Eli<br><br><br><br></div>