Mercurial, D/VCS non-versioned files

[Giorgos Keramidas]

On Thu, 18 Dec 2008 08:40:00 +0100, Martin Geisler <mg at daimi.au.dk> wrote:
>Arne Babenhauserheide <arne_bab at web.de> writes:
>> If you can't go this way, giving them unversioned files and
>> reversioning their changes is easy in Mercurial. Here's one example:
>>
>> Just create one clone for each designer and when they come back with
>> their files put them into the workdir of the clone you prepared for
>> them.
>
> A variant of the suggestion above is to use 'hg archive' to create a
> zip or tar.gz file that you can give to your designers. The file will
> contain a .hg_archival.txt file which contains two lines like this:
>
>   repo: 3defa349e8bb19147ab520bef475e19bf9a62178
>   node: 2fad0743f8ba61c1f13ebdc57ce5235cd45ea0a3

That's a good idea.  It may even make sense to use local tags to track
which revision has been given to each designer, i.e.:

    hg tag -l giorgos-keramidas-2008.12.18
    hg archive -t files -r giorgos-keramidas-2008.12.18 ~/files

Then as long as the local tag exists, you can go back and diff with the
file drops that the particular designer pushes back your way :)