Tracking base revision for files distributed without a repo

[Bob Hood]

On 1/24/2014 2:47 AM, Dirk Heinrichs wrote:
> Am 23.01.2014 06:47, schrieb Benjamin Fritz:
>> Are there better solutions than just embedding the revision in the
>> file using KeywordExtension? Solutions that allow my coworkers to
>> continue being lazy but allowing me to benefit from knowing which
>> version they base any changes off, what to tell them I've changed
>> since the last time I sent them updates, etc.?
>
> Use branches. One for each of your co-workers. Merge your work to a
> co-workers branch before you hand it over to him, commit what you get back
> to the same branch.

+1

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20140124/5dc04300/attachment-0002.html>