Mercurial workflow for private branches with multiple machines, serving a single central repo?

Just use separate repos for "central" and "in progress". Have your central, meaningful repo be the place where you push changes you're ready to share with the world, and until you're ready to release them push them to a separate '-devel' repo. Push and pull to that from all your machines and promote -devel into formal with a 'push' when you're ready You can get fancier and use a patch queue (mq) in devel that is itself version controlled, if you don't want the resulting changesets to necessarily match your in-progress changesets, but I'm a fan of exposing the process as much as the result, so I don't go that route Either way though push and pull are all you need to keep in-progress work going to/from a -devel repo (or versioned queue) and then migrate up to central when you're ready (The LocalBranch extension suggested in a comment on the question itself isn't at all what you want as they don't migrate between machines at all -- hence their name.).

Just use separate repos for "central" and "in progress". Have your central, meaningful repo be the place where you push changes you're ready to share with the world, and until you're ready to release them push them to a separate '-devel' repo. Push and pull to that from all your machines and promote -devel into formal with a 'push' when you're ready.

You can get fancier and use a patch queue (mq) in devel that is itself version controlled, if you don't want the resulting changesets to necessarily match your in-progress changesets, but I'm a fan of exposing the process as much as the result, so I don't go that route. Either way though push and pull are all you need to keep in-progress work going to/from a -devel repo (or versioned queue) and then migrate up to central when you're ready. (The LocalBranch extension suggested in a comment on the question itself isn't at all what you want as they don't migrate between machines at all -- hence their name.).

What I usually do is use bookmarks or locally-created nambed branches in Mercurial. The local named branch will lose its name when it gets pushed to Subversion, and the bookmark is transient anyway. That lets you avoid having tons of repositories laying around and keeps things clean(er).

Pushing and pulling "behind svn's back" can lead to a slightly confusing set of revisions from time to time, since hashes necessarily change when you push to Subversion.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.