typo in help message. From: "Aneesh Kumar K.V" <aneesh.kumar@hp.com>

Update tests

Catch SIGHUP This should reduce the chance that a repo we're connected to via ssh gets interrupted without doing rollback.

Switch push over to the new scheme Now push works transparently with any repo with lock and addchangegroup. Currently this is local repos and ssh.

Add addchangegroup to the ssh protocol

Add a scheme for handling remote locking This adds an object that remembers to unlock the remote repo on destruction and lock/unlock functions for the ssh protocol. The remote repository should also unlock itself when the connection goes down.

Fix up the broken bits in findoutgoing

Move the empty changeset detection out of findincoming to pull This lets us reuse findincoming for findoutgoing

Protocol switch from using generators to stream-like objects. This allows the the pull side to precisely control how much data is read so that another encapsulation layer is not needed. An http client gets a response with a finite size. Because ssh clients need to keep the stream open, we must not read more data than is sent in a response. But due to the streaming nature of the changegroup scheme, only the piece that's parsing the data knows how far it's allowed to read. This means the generator scheme isn't fine-grained enough. Instead we need file-like objects with a read(x) method. This switches everything for push/pull over to using file-like objects rather than generators.

Add a repo method to report repo device This is used to establish whether repos are on the same device for hard linking. Remote repos all return -1.