Tracking base revision for files distributed without a repo

[Harvey Chapman]

On Jan 23, 2014, at 12:47 AM, Benjamin Fritz <fritzophrenic at gmail.com> wrote:

> But when they occasionally email me back a modified copy of the script
> to fix a bug or expand the types of data it can handle, I'd really
> like to know where to start when merging in changes. They always send
> back just the modified files, not the directory I sent them, so I

"hg archive DEST” will place a “.hg_archival.txt” file at the root of DEST containing the following:

repo: 5740712d89b860684866f0578b399d7f294f651b
node: 5471870d1391985090e35334347d9085bdf57fa0
branch: default
latesttag: null
latesttagdistance: 33

Perhaps your co-workers would be willing to send you that file?