I just pushed a couple of changesets.  Right after typing 'hg push' I
realized that the date was messed up on one of them, so I typed ^c to try
and abort, but apparently managed only to abort the execution of the
post-commit hooks (e.g., sending the email notification) and not the commit
itself.  It didn't seem worth trying to roll back etc., so I'm just sending
out this manual notification instead.

Here are the two changesets that were pushed:

changeset:   11370:af870035ab6b
tag:         qparent
user:        Steve Reinhardt <[email protected]>
date:        Sun Mar 13 17:47:33 2016 -0700
files:       src/SConscript
description:
scons: fix building in non-standard locations

It's apparently not widely known that our scons scripts allow you to
put the build directory wherever you want; not only does it not have
to be immediately under the root of your repo, it doesn't even have
to be underneath the root at all.  (For example, sometimes it's useful
to build on a local disk if your repo is on a slow NFS mount.)

I point this out because this functionality has been broken for close
to two years but no one seems to have noticed yet.  This patch fixes
an assumption that crept in in changeset be0e1724eb39 (May 09 2014)
that the build dir would be immediately under the top level of the
repo, preventing builds anywhere else.


changeset:   11369:0c1ae495b5e4
user:        Steve Reinhardt <[email protected]>
date:        Thu Feb 18 10:42:03 2016 -0500
files:
tests/quick/se/04.gpu/ref/x86/linux/gpu-ruby-GPU_RfO/config.ini
tests/quick/se/04.gpu/ref/x86/linux/gpu-ruby-GPU_RfO/simout
tests/quick/se/04.gpu/ref/x86/linux/gpu-ruby-GPU_RfO/stats.txt
description:
stats: update gpu-ruby-GPU_RfO stats

Output changed way back in this cset:

changeset:   11345:b6a66a90e0a1
user:        John Kalamatianos <[email protected]>
summary:     gpu: fix bugs with MemFence, Flat Instrs and Resource
utilization
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev

Reply via email to