On Sun, Mar 13, 2011 at 14:41, Nick Coghlan <ncogh...@gmail.com> wrote:
> On Sun, Mar 13, 2011 at 8:32 AM, Eli Bendersky <eli...@gmail.com> wrote: > > 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. > > > > 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. > > Since I have multiple machines to keep in sync, I'm actually thinking > a server side sandbox clone is the way to go. That will solve my local > issue as well (since the sandbox clone will be separate from the main > clone). > This is precisely what I do, since I routinely commit to personal Mercurial repos from 3 different machines. Eli
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
