That's quite an oversimplification of the problem, copying stack/heap/etc. Anyways, check out CRIU as a starting point.
Yeah, it's interesting how many people have had the same idea at some point or another. I was fiddling around with Rails and AWS for a bit around 4 years ago and used the same idea for a tiny project. It's a bit like…
$120k in Seattle is not equivalent to $120k in the Bay Area...
Nothing unless you're rebasing upstream, but I think the point he was trying to make was that you should always run `git fetch` and then `merge` from there (again, there are some situations where the pull is fine IMHO).
That's quite an oversimplification of the problem, copying stack/heap/etc. Anyways, check out CRIU as a starting point.
Yeah, it's interesting how many people have had the same idea at some point or another. I was fiddling around with Rails and AWS for a bit around 4 years ago and used the same idea for a tiny project. It's a bit like…
$120k in Seattle is not equivalent to $120k in the Bay Area...
Nothing unless you're rebasing upstream, but I think the point he was trying to make was that you should always run `git fetch` and then `merge` from there (again, there are some situations where the pull is fine IMHO).