Tracking base revision for files distributed without a repo

[gadgetsteve]

The advantages would be that it would automatcally produce a zip file with the commented tag in for you.


Sent from Samsung Mobile

<div>-------- Original message --------</div><div>From: Benjamin Fritz <fritzophrenic at gmail.com> </div><div>Date:23/01/2014  06:46  (GMT+00:00) </div><div>To:  </div><div>Cc: Mercurial Mailing-list <mercurial at selenic.com> </div><div>Subject: Re: Tracking base revision for files distributed without a repo </div><div>
</div>
On Thu, Jan 23, 2014 at 12:01 AM, Steve Barnes <gadgetsteve at hotmail.com> wrote:
> On 23/01/14 05:47, Benjamin Fritz wrote:
>>
>>
>> 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.?
>>
> I personally would use a little python distribute script to add a comment
> that includes the revision ID in each file as a comment as it zips the
> files.  If use os.walk and zip you can easily do this. Let me know if you
> would like a draft of something along those lines.
>

What does this offer over the use of KeywordExtension? It seems like
just an extra step to run every time I share changes to accomplish
much the same thing.
_______________________________________________
Mercurial mailing list
Mercurial at selenic.com
http://selenic.com/mailman/listinfo/mercurial
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20140123/b81702fa/attachment-0002.html>