Tracking base revision for files distributed without a repo

[Dirk Heinrichs]

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.

HTH...

    Dirk
-- 

*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 1596666 (Ansage) 1149
*Email*: dhs at recommind.com <mailto:dhs at recommind.com>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>



http://www.recommind.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20140124/538f5b90/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1537 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20140124/538f5b90/attachment-0002.gif>