[m5-dev] upstream changeset in output

[Gabe Black]

   I've been thinking about how this could actually be done, and it 
seems to me that there could be a hook in the head (hooks are 
propagated, right?) which adjusted a header file every time a changeset 
was pushed into the head to have that hex value in a variable. The 
adjustment to the header file would be part of the changeset so that 
moving around revisions would keep it consistent, and I don't know if 
you could really do it any other way. That would ensure that unless the 
downstream users explicitly modify that header file for some reason, 
which would be a little weird, the output would reflect the last 
changeset that was stamped by the root. One downside to all this is that 
that file would change constantly and clutter the history and the 
repository metadata.

Gabe
_______________________________________________
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev