Yea, I thought it would do the trick...obviously not! I was adding the message as : hg qrefresh -m "....\n...."
So I guess I have to commit in a real text editor to get the newline to show. On Sat, Apr 18, 2009 at 12:16 PM, Steve Reinhardt <[email protected]> wrote: > I"m not sure what you did with your patches, Korey, but a literal '\n' is > not the same as an actual newline :-). > > Steve > > On Fri, Apr 17, 2009 at 9:36 AM, Steve Reinhardt <[email protected]> wrote: >> >> Also, on a totally unrelated note, recall that the first line of your >> commit message should be a one-line stand-alone summary. What you have here >> would be OK if you just put a newline after the first period. I think Nate >> is pushing us to use labels, something like "branch pred: fix for MIPS". >> >> Steve >> >> On Wed, Apr 15, 2009 at 8:06 PM, Korey Sewell <[email protected]> >> wrote: >>> >>> # HG changeset patch >>> # User Korey Sewell <[email protected]> >>> # Date 1239850525 14400 >>> # Node ID ce539a58327b78b049f8af0bf8a00737f2b97640 >>> # Parent 7b685fee8773c2fe0bd09ec7abb0a43873aeed92 >>> Fix Branch Prediction for MIPS. Namely, i dont see the reason for >>> updating the branch history on anything that happens in decode. this should >>> happen only in commit, right? >> > > > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev > > -- ---------- Korey L Sewell Graduate Student - PhD Candidate Computer Science & Engineering University of Michigan _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
