Committing changes to an un-checked out revision

[Michael Diamond]

Hey all,

I'm willing to accept that perhaps this is a terribly bad idea, but I'm
wondering about the feasibility / soundness of the following idea:

I want to be able to take either a set of files or a diff and tell
Mercurial "Commit this data as a changeset off of revision X" even if
that's not the revision that's checked out, or no revision is checked out
(like on a central Mercurial server).

The idea being to enable programatic commits to any revision, without
needing to a) use up the space of having a working directory checked out or
b) lock the repository to one user's transactions at a time.

An example senario: use Mercurial as the history storage for a wiki. Users
can clone their own private version of the wiki if they want, but they can
also edit the central version as well via a web frontend. The frontend then
has the ability to directly commit changes against the revision the user
was editing from, and merges are handled automatically or handed to the
user to resolve if necessary.

I'm not specifically looking at a wiki, but I generally really like the
idea of using Mercurial to track history of different types of data than
just source code, and understanding the possibility / limitations of
automated commits seems central to this idea.

Thanks,

Michael

Michael Diamond
dimo414 at gmail.com
www.DigitalGemstones.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20120815/5a0a2f10/attachment-0002.html>