Hello,<br><br><div class="gmail_quote">On Tue, Sep 18, 2012 at 1:25 PM, Ian Lynagh <span dir="ltr"><<a href="mailto:ian@well-typed.com" target="_blank">ian@well-typed.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Why do you want to build 7.6 but not 7.6.1, OOI?<br>
<div class="im"><br></div></blockquote><div> I was trying to build a different branch which is a fork of 7.6---I wanted to play around with the profiling suite described in the "Core Diving" talk from the Haskell Implementors workshop.</div>
<div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
> More generally, I run into this problem all the time with people trying to<br>
> build the branch I work on, so it really would be nice if we started using<br>
> sub-modules to keep track of this dependency. I talked to folks at ICFP<br>
> about this, and one idea was that we could check in the "fingerprint" for a<br>
> branch into the repo, and track the dependencies this way, but this is<br>
<br>
</div>See<br>
<a href="http://hackage.haskell.org/trac/ghc/wiki/Building/GettingTheSources#Trackingthefullrepositorystate" target="_blank">http://hackage.haskell.org/trac/ghc/wiki/Building/GettingTheSources#Trackingthefullrepositorystate</a><br>
<br>
The nightly build logs include a fingerprint.</blockquote><div> </div><div>Where are the nightly build logs?</div><div><br></div><div><br></div><div> > exactly what git's submodule machinery does, so it seems pointless to</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
> implement the functionality which is already there with a standard<br>
> interface. Thoughts?<br>
<br>
</div><a href="http://hackage.haskell.org/trac/ghc/wiki/DarcsConversion#Theperspectiveonsubmodules" target="_blank">http://hackage.haskell.org/trac/ghc/wiki/DarcsConversion#Theperspectiveonsubmodules</a><br>
<br></blockquote><div><br></div><div>I have seen this. Our custom "fingerprint" solution has the exact same drawbacks (because it does the exact same thing as sub-modules), and in addition it has the drawback of</div>
<div> 1. being a custom non-standard solution,</div><div> 2. it is not obvious where to find the "fingerprint" associated with a particular branch (which is what lead to my question in the first place).</div><div>
<br></div><div>-Iavor</div><div> </div><div> </div></div>