[mythtv-users] git & wiki

Gavin Hurlbut gjhurlbu at gmail.com
Thu Dec 9 07:50:08 UTC 2010

On Wed, Dec 8, 2010 at 7:32 PM, E. Westbrook <mythtv-users at westbrook.com> wrote:
> Just as another way:  To keep it numeric, increasing, and consistent, I'm
> currently numbering my Gentoo ebuilds using the unix integer commit
> timestamp of the commit at the point in question, which I can capture when
> checked out to the right HEAD using:
> $ echo 0.24.$(git log -n1 --pretty="format:%ct")
> 0.24.1291777173
> In reverse, I obtain the commit hash from that point in time on that branch
> with:
> $ echo $(git log -n1 --pretty="format:%H" --since=1291777173
> --until=1291777173)
> hash = ee57332927393d071d7b3f1788476f07c77f7e82

This is a bad plan.  The reason for that is, there can be more than on
simultaneous commit at any second on a single branch.  It won't happen
often, but it can, and therefore eventually will, happen.  Which one
the fancy git log pulls out may or may not be indeterminate.  How can
this happen?  Easily.  Two developers independently commit to their
local trees at that same moment in time.

If you use a methodology like this, first, be very careful at what
timestamps you capture.  Do so when there's no concurrent work (which
you may not know in advance if the other branch is not pushed yet).
Secondly, you might as well use human readable dates if you're going
to do that. :)

Just my thoughts.

Now, all you individual gentoo ebuild creators... you are wasting lots
of time (thankfully it's your time) by duplicating efforts.  I know of
at *least* 4 different ebuilds being worked on at the same time.
Wouldn't it be wiser to pool your brainpower and time and do it
*once*?  Again, your time to waste, but...

More information about the mythtv-users mailing list