Question about pretxnchangegroup

[Douglas Philips]

On or about 2008 Nov 10, at 3:56 PM, Dennis Brakhane indited:

> On Mon, Nov 10, 2008 at 9:14 AM, Maxim Vuets <maxim.vuets at gmail.com>  
> wrote:
>> You can make autobuild daemon and some kind of FIFO.
>> 1. Developer clones shared, does changes, commits them to gate
>> 2. Gate's hook passes last-known-working-rev (current state) and
>> expected-tip-rev (commited changes) to autobuild daemon's FIFO.
>> 3. Daemon performs in background build, testing and
>> a) pushes changes from gate to shared in case of succeess
>> (hg push --rev may be used also), or
>> b) strip commited changes in case of failure.
>
> Wouldn't that result in completely different changesets (rev.
> numbers), and therefore
> I an lot of merges once a developer pulls from shared?

Nope. A changeset is a changeset is a changeset.

You might get a different (local) revision number based on the order  
in changesets are pulled (*), but the real id (the long hex number)  
never changes because of a pull, push, or anything else. Once a commit  
happens, its changeset id -never- changes.

--Doug

(*) - http://www.selenic.com/mercurial/wiki/index.cgi/UnderstandingMercurial#head-fae64e13fd85cc535f9ae209f35c4a4477a7ac24