<div class="gmail_quote">On Fri, Dec 3, 2010 at 10:07, Gavin Hurlbut <span dir="ltr"><<a href="mailto:gjhurlbu@gmail.com">gjhurlbu@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Fri, Dec 3, 2010 at 8:49 AM, Bill Meek <<a href="mailto:keemllib@gmail.com">keemllib@gmail.com</a>> wrote:<br>
> +SOURCE_VERSION=$(git --no-pager log -1 --format="%h" 2>/dev/null ||<br>
<br>
</div>Not what we plan on using anyways. This is on the list to fix today,<br>
so just relax, people :)<br></blockquote><div><br>May I kindly request a "heads up" when you guys feel this is done and ready for general consumption.<br><br>I prematurely started working on updating my distro packaging scripts yesterday, then backed out after the github repo was recreated (and the mythweb subtree "poofed" out from under me, lol). So I figured I'd wait for things to stabilize.<br>
<br>It would be fantastic to know when you guys feel it has mostly settled -- or has it already yet?<br><br>Also, what will become the "proper" way to refer to past (formerly HEAD) commits on branches like the fixes/0.24 branch? I would suspect that the SVN "changeset" notation is going away in lieu of git nomenclature, yes?<br>
<br>In my previous scripts, I numbered my package revisions like "0.24.27396", and I'm looking forward to determining what minimal but precise numbering scheme I'll use now, as well as how I'll retrieve source snapshots for each. The old system's ability to get a source tree zip file just by specifying the changeset number in a specially-crafted URL was fantastic, although it's certainly easy enough to emulate that locally with git scripting if need be.<br>
<br>Not trying to push anyone... I'm sure this stuff is already being (or already has been) thought about... I'm just eager to know the details and get to work on this end.<br><br>Standing by patiently for more info.<br>
<br>Thanks!<br>EW<br></div></div>